I've written mobile E2E tests three ways now.
Detox
Painful. Flaky tests, long setup, and every small UI change broke something.
Maestro
Made it easy. Simple YAML, and it just worked.
Now: e2e by TesterArmy
You write the test in plain English, like "upgrade the workspace to the Pro plan," and an agent drives the app to do it.
The clever part: once a step passes, it records what the agent did. After that it just replays those actions, with no AI call, until the app changes. So it doesn't cost money on every run, and you don't get a different result each time.
It works on iOS and Android simulators, and there's an Expo example.
My take
It's still pre-1.0, so I wouldn't move a critical suite onto it yet. But it's interesting to see where testing is heading.
What are you using for mobile E2E right now?
Top comments (1)
That replay boundary is the part I'd test before trusting it for a release gate. If the app changes but recorded taps still land somewhere, the test can pass the wrong path unless it asserts the resulting state, not just the action sequence. I'd keep Maestro for deterministic auth or purchase paths and use an agent to explore new screens. Does the replay verify post-action state, or only repeat the recorded steps?