-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Widget unit testing with emoji_picker_flutter
#156
Comments
Hey @LuchoTurtle, thanks for reporting this issue. The |
Thanks for the reply :) I've found a way so However, the only way I got this to work is having to disable the "Recents" emojis tab. Config(recentTabBehavior: RecentTabBehavior.NONE); This was the only way I could find to So hopefully this helps people in the future :). Though it'd be fun to have a neat utility function that would allow us to input emojis without having to go through these hoops. 馃憖 |
Version 2.0 will include some basic tests. Thanks again @LuchoTurtle for your help 馃檹 I will close this issue with the release of version 2.0. |
Hey there! 馃憢
Thanks for the package, it's mighty useful!
I'm having a bit of trouble widget-testing an application that includes this package. Since there aren't any testing utilities that I can go for, to test my code I'm doing something like this in my test:
I'm always setting the size of the unit test to always be the same one so it works every time. The thing is, I'm simulating this test on a physical device and everything works out - it clicks on an emoji and it is inserted as text. You can check it in the video below:
23-09-26-16-03-51.mp4
However, even though all the unit tests pass and the integration tests pass, it seems the callback of the inserted emoji is not covered.
Has this happened to y'all? Why is the
onEmojiSelected
callback not being invoked during unit tests and being covered?If you're curious, you may see the offending file in https://github.com/dwyl/flutter-wysiwyg-editor-tutorial/pull/9/files#diff-64157eac151a0f2a28dff32d284fc4f62e2eaf53e0dd0a8c1cd31e77f56e700d.
Thank you!
The text was updated successfully, but these errors were encountered: