mini now works in Jira

AI for QA teams: regression pack automation

Your judgement. mini’s repetition.

mini writes, maintains and runs every regression test. Your team makes the calls.

mini takes the repetition.

  1. mini writes the suite.

    Scenarios and acceptance criteria, from your app, repo, specs and test cases.

  2. It keeps the suite current.

    Proven fixes apply on their own. An app bug gets one Slack message. Revert in one click.

  3. No selectors to break.

    mini reads the screen, so a moved button doesn’t turn the suite red.

  4. The flows scripts can’t reach.

    Up to three phones in one test, email codes, deep links, mocked GPS.

Will mini replace us?

No, but the work changes. The rerunning goes to mini; the judgement stays with you.

mini takes

  • Writing the regression tests and updating them as the app changes
  • Running the whole suite on every release, on iOS, Android and web
  • For every failure: the recording, failed criterion, device log with any crash and steps to reproduce
  • Flagging what no criterion asked about, as suggestions you keep or dismiss

Your team keeps

  • What counts as a bug, what goes to a ticket and what ships
  • Exploratory testing and the new features nobody has tested yet
  • The criteria mini tests against, edited whenever you want
  • The release sign-off, with a report mini prepares

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

From a pilot customer.

  • Helmit
  • Memrise
  • Nanogram
  • Impakt
  • Trippin
  • MindStash
  • Clutch

Good questions.

What happens when mini gets it wrong?

Mark the issue Not a bug and tell mini why in a sentence. The issue stops counting against the app, and mini puts your note to use on the next run, so it doesn’t raise the same false alarm on the next run. You can also edit the criterion or mini’s notes about your app.

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. The device log sits beside it, with a jump to any crash. If mini can’t grade a test, because the build broke or sign-in failed, it’s marked Unprocessable.

How long does a full regression take?

Tests run in parallel across your devices and browsers, so run time depends on your suite and how many run at once, and a running test shows its estimate with a likely range. One pilot customer went from 2 days to 1 hour. Your plan sets how many devices and browsers run at once.

Can we start from the regression pack we already have?

Yes. Upload the test cases and specs you already have, 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.

We already have automation. Do we throw it away?

No. Keep your unit tests and your scripts. mini runs next to them and takes the end-to-end regression your team still runs by hand, plus the flows your scripts can’t reach.

Can we choose the accounts, codes and devices?

Yes. mini signs in with your test accounts, reads email codes and magic links from its own inboxes, and uses a fixed code you set for SMS. Tests run on iOS simulators, Android emulators and browsers, and on real iPhones and Android phones (Samsung Galaxy, Google Pixel, Redmi, OnePlus, Huawei and more) from our managed farm, enabled per workspace. mini can also seed test data through your app’s own test endpoints, and reset it with a webhook you set per app.

Where do findings show up?

In the Minitap app, in a Slack thread per issue with Not a bug and Resolved buttons, as a comment on GitHub pull requests to your main or release branches, and as a check on every run. Send any issue to Jira, Linear or Notion as a new ticket, or link one you already have. Mention @mini in a Jira comment and it runs the scenario and answers in the thread.

What can’t mini test?

Face ID and fingerprint, NFC, Bluetooth, real SMS and calls, real payments, and native tablet and watch apps, or TV apps beyond Android TV. Payments run in the store’s sandbox or with a test card. In-app purchases run on a real iPhone with a Sandbox Apple Account, or in a StoreKit test store on simulators. Nobody is charged.

Can we share a run with people who never open Minitap?

Yes. Export any run as a one-page sign-off or a full report with a screenshot of each failure, as a PDF, or as a CSV with one row per check.

Can mini run the suite every night?

Yes. Schedule the whole suite, a tag or picked scenarios, on the latest build, a fixed build or a branch. Each run posts one message to Slack: passed, failed, skipped and new bugs, with a link to the run.

Bring the pack you’re tired of running.

Bring a build and your three hardest flows. A pilot comes first, and you keep the suite.