A note of warning: if you are in a Flutter project that won’t take more than 3 months, you won’t need an extensive testing approach, therefore you won’t need the approach that I suggest in this post.
But. . .
If you work in a Flutter project that will take a long time, I would strongly advise investing in testing, and that includes:
Flutter Driver Tests
I’ve mentioned that Flutter Driver Tests have its issues:
- Require iOS/Android device
- Slower than Widget Tests
- Dependency Injection is problematic
- Tests depending on the outcomes of the previous tests
- Running one test file at a time
- Difficult to debug failing tests
Fortunately, I’ve mentioned that those issues can be solved. . .
Unfortunately, it would have taken you a lot of code to do that.
What if, there were a command-line tool that could do the majority of work for you?
Yes, there is — why else would I write this article?!
We’ve released a package that does most of the work for you. In my company, we are using this package internally, but I would love to hear your feedback on any feature requests.