I’ve been using Maestro for two very large Flutter apps and it’s been so ahead of every other option is not even funny.
No long compilation times, no half baked testing dev experience, supports iOS and Android, no pumpAndSettle BS, No Flutter hacks, multiple cloud providers (cloud.mobile.dev, moropo), you can interact with native elements, so you can work with push notifications, system dialogs, system settings, email clients, web views, browsers, and a very simple test definition files that every capable QA engineer can maintain with very little supervision from developers (no need for dart expertise for writing tests).
haha happy to hear that :) (I created Patrol) ((and then worked on Maestro at mobile.dev briefly))
I too think that for the vast majority of use cases, Maestro is the best solution. Fast and easy to write and run.
Also it's cool that it's open-source and has very strong community. I'd be skeptical to have all my tests stored in some SaaS that I can't even run locally (as some other solutions do)
Maestro being open source, being able to run it locally AND having two providers where we can just sign up and start running our tests was an important factor going with them.
We ended up going with Moropo as their pricing matched our needs better. Even if in the future we had issues with them, we could just go to a different provider is a big plus.
No long compilation times, no half baked testing dev experience, supports iOS and Android, no pumpAndSettle BS, No Flutter hacks, multiple cloud providers (cloud.mobile.dev, moropo), you can interact with native elements, so you can work with push notifications, system dialogs, system settings, email clients, web views, browsers, and a very simple test definition files that every capable QA engineer can maintain with very little supervision from developers (no need for dart expertise for writing tests).
I can only recommend it.