Automated regression testing for mobile apps
Hand mini the full regression.
mini writes it, keeps it current and runs it every release: iOS, Android, web.
The subtotal matches the items in the cart
- Family pizza box$46.50
- Garlic bread$8.99
- Caesar salad$12.99
- Lemonade ×2$14.00
- Family pizza box$46.50
- Garlic bread$8.99
- Caesar salad$12.99
- Lemonade ×2$14.00
The whole suite, every release.
Tests that keep up with your app.
mini writes, runs and updates them. Your team decides what ships.
No selectors to maintain.
mini reads the screen, so a red test points at the app.
Real devices and simulators.
Simulators, emulators and browsers in parallel. Physical phones per workspace, on request.
Every failure shows its proof.
The recording, the failed criterion, expected versus seen, and the last pass.
Teams that ship with mini.
“We've been working with Minitap for a long time on our mobile apps. They are exceptionally flexible, always ready to adapt their product to our workflow, and their solutions help us verify our apps reliably.”
Mikalai DzmitryieuSenior Software Engineer, Memrise- 2 days → 1 hourFull regression
- 48 hoursTo full coverage
- WeeklyReleases, from fortnightly
From a pilot customer.
Helmit
Memrise
Nanogram
Impakt
Trippin
MindStash
Clutch
Click through a real run.
Our food-ordering demo app: 12 tests on iOS and Android. The runs and bugs are real.
Cart Management
Manage Cart Contents
Critical7/8 passed · Android
- Expected
- Confirm the price summary shows a subtotal, delivery fee, and grand total that reflect all items
- Actual
- Cart subtotal does not match the sum of line prices — overstates by $1.50 per cart line, inflating the grand total.
Can we start from the regression pack we already have?
Yes. Upload your existing test cases and specs, connect your repository, and mini explores the app. It writes its tests from all of it, and your team can edit any test in plain words.
Who reviews what mini writes?
Your team, as closely as it wants. Each test is a scenario and its acceptance criteria in plain words, and every change mini makes to the suite is listed for you to check and send back. What ships is always your team’s call.
Does mini replace our testers?
No. mini takes the repeat work: writing, running and updating the regression suite on every release. Your testers decide what counts as a bug, check what mini changes when they want to, and spend the time on new features and exploratory testing.
How do we know a pass is real?
Each acceptance criterion carries its evidence: what mini saw, a screenshot, the moment in the recording and how confident mini is in the grade. If mini can’t grade a test, because the build broke or sign-in failed, it’s marked Unprocessable, never passed.
How long does a full regression take?
Tests run in parallel across your devices and browsers, so a full regression usually takes about an hour. Your plan sets how many devices and browsers run at once.
What does it cost for a suite our size?
Plans are sized by how many full regressions you run a month and how many devices and browsers run at once. For a large suite, we scope the plan with you on your own tests.
What happens when the app changes on purpose?
mini tracks your code, specs and tickets and updates the suite to match: new tests for new features, edited criteria, and stale tests retired. With the GitHub integration this happens on its own; without it, you start it from the CLI.
Does it run in our CI?
Yes. GitHub is native: a comment on every pull request to your main or release branches, a check on every run, and a GitHub Action for release runs. Checks inform by default and you choose when they block. Any other CI starts runs through the minitest CLI. Jira or Linear tickets from an issue are available on request.
What can’t mini test?
Face ID and fingerprint, NFC, Bluetooth, real SMS and calls, real payments, tablets, watches and TV. Payments run in the store’s sandbox or with a test card.
Bring your three hardest tests.
We run mini on your build during the call. You keep the report.