How Doist orchestrates its UI test suite with Maestro
Original post Orchestrating our UI test suite with Maestro
Article Summary
The Doist Android team's UI test suite had become so flaky that only 50% of runs passed on the first try. Their solution? A complete migration to Maestro that changed everything.
Doist's Android team was stuck in a maintenance nightmare with their Espresso-based UI tests. Flaky tests meant PRs sat for over an hour waiting for reruns, and engineers needed deep knowledge of complex IdlingResources just to write reliable tests. They decided to migrate their entire end-to-end test suite to Maestro's black-box approach.
Key Takeaways
- Test reliability jumped from 50% to 99%+ after migrating from Espresso to Maestro
- Runtime dropped 4x to under 20 minutes by batching flows strategically
- Testing costs cut 50% (from $2000/month) with fixed subscription pricing
- Zero production code changes needed, no more maintaining fragile IdlingResources
- Built custom Firebase webhook system to report failures in Twist daily
By switching from Espresso's explicit synchronization to Maestro's polling approach, Doist achieved 99%+ test reliability while cutting costs in half and eliminating maintenance burden.
Continue reading
This page summarizes “Orchestrating our UI test suite with Maestro” by Doist, published Nov 20, 2025. All credit for the original work goes to the authors.