Mobile QA coverage you don’t have to hire for.
If you’re shipping iOS or Android without a QA team of your own, miniTest is for you. Mini, the agent behind it, is an AI QA engineer. It picks a build and runs the stories you care about on a virtual device, then ends every run with a verdict.Passed
Everything worked. The build is safe to release.
Failed or Warning
Mini found a bug. You get the video, the repro, device logs, and a fix prompt ready to paste into Cursor or Claude.
How it works
1
You bring your codebase
Connect your repo and Mini reads it to draft user stories that match your app. No repo to connect? You can upload an iOS or Android build directly instead.Then add a few sentences about the user stories that matter: the ones you’d never want broken. Sign-in. Checkout. Anything that touches revenue.
2
Mini owns the suite
You describe what should work in plain English. No selectors, no YAML, no fixtures.Your app keeps changing, and the suite falls behind it: a button moves, a screen gets rebuilt, a whole feature ships. Mini keeps the suite caught up with what’s actually in the app, so your coverage matches this week’s build instead of last sprint’s.When something fails, you don’t have to go digging. The issue comes with a fix already drafted.
3
You decide to ship
Mini writes the stories, runs them, keeps the suite up to date, and triages whatever fails. Whether to ship is still your call.
Where to go next
Meet Mini
The agent behind every run, every triage thread, and every Slack message.
Quickstart
Run your first user story on a virtual device. About fifteen minutes.
Anatomy of your suite
What a user story looks like, and how acceptance criteria become the source of truth.
Reading a run report
Where you’ll spend most of your time once the agent is running.