mini now works in Jira

AI mobile app testing platform for iOS, Android and web

Every test, written and run by mini.

Real devices, simulators and browsers. Cross-app, GPS and multi-device flows included.

Book a demoSee a real report

The hard parts, handled.

  • No flaky tests.

    No selectors or coordinates. After a redesign, mini checks the same criteria.

  • Two phones. One test.

    Up to three phones on the same OS.

  • Out of the app and back.

    Email codes, magic links and Sign in with Google.

  • Anywhere on the map.

    A mocked location or route, iOS and Android.

  • mini speaks up before you ask.

    Flags issues no test asked about, and asks in Slack for accounts.

  • In-app purchases, end to end.

    Subscriptions in Apple’s sandbox on a real iPhone, or a StoreKit test store on simulators. Nobody is charged.

    Example: on a real iPhone enabled per workspace, a paywall offers Pro at $4.99 a month. mini taps Subscribe, Apple’s sandbox sheet opens for a Sandbox Apple Account, mini confirms, and the app shows Subscribed · Sandbox. mini notes that nobody was charged, and the test passes.

mini writes the suite.

Each test is a scenario and its acceptance criteria.

  • From what you already have.

    Your app, repo, Notion specs, Jira tickets and test cases.

  • Written as outcomes.

    mini finds the way through on every run.

  • Yours to change.

    Edit tests in plain words from the dashboard, Slack or your agent. Tag them, run by tag.

  • See what mini knows.

    Every answer cites its source: GitHub, Notion, Jira or your team.

Real devices and simulators, in parallel.

The whole suite at once. Real iPhones, Galaxy, Pixel, Redmi, OnePlus and Huawei phones per workspace.

  • Browsers too.

    Desktop Chrome, Firefox and Edge, Safari on iPhone, Chrome on Android.

  • Your build, or ours.

    Upload an .apk, .aab or iOS build from CI, use TestFlight, or mini builds each commit.

  • Test data, set up first.

    mini seeds accounts through your test endpoints.

  • Behind your firewall.

    On Enterprise, a private connector reaches your staging, and devices can use VPN mode.

Every finding comes with its proof.

One issue per failed criterion, with the recording, what mini expected and what it saw.

  • Ready for a developer.

    Steps to reproduce, the device log with the crash, and a fix prompt for your agent.

  • Not a bug, said once.

    Dismiss with a reason; mini remembers.

  • Beyond pass and fail.

    UI/UX issues, plus iOS and Android WCAG 2.2 audits, on request.

  • A report anyone can read.

    A one-page sign-off or the full report, as PDF or CSV.

Tested before it merges.

mini tests a pull request when you ask and comments with what broke.

  • Start it your way.

    Comment @mini test, or use the GitHub Action.

  • Other CI, coding agents too.

    Any CI via the CLI, coding agents via MCP.

  • In your Slack.

    Findings land in your channel, and each scheduled run sends one summary.

  • In Jira, Linear and Notion.

    Mention @mini in a Jira comment. Send any issue to a ticket, or link one you have.

Ship a redesign. Keep the tests.

Tests say what must be true, whatever the layout.

  • New features, new tests.

    mini adds, edits and retires tests as your code and specs change.

  • Proven fixes, applied.

    A fix mini proves on a device applies on its own. Revert any in one click.

  • One Slack message.

    An app bug or a stuck test gets one message. Prefer to review first? Turn it on.

  • Works without GitHub.

    Start it from the CLI; your coding agent proposes the edits.

Every capability.

Test

Run

Review

Work with mini

Teams that ship with mini.

“For the first time, I ran a pilot without a single technical bug. Testing my native iOS and Android apps in real conditions let me catch bugs upstream. Minitap saves me time and gives me confidence in every release.”
Sandra KhirecheFounder, Impakt
  • 2 days → 1 hourFull regression
  • 48 hoursTo full coverage
  • WeeklyReleases, from fortnightly

From a pilot customer.

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

Good questions.

Regression testingAccessibility testingPricingSecurity and enterprise
Which devices and browsers does mini run on?

iOS simulators and Android emulators in the cloud, plus real iPhones and Android phones (Samsung Galaxy, Google Pixel, Redmi, OnePlus, Huawei and more) from our managed farm, enabled per workspace. On the web: Chrome, Firefox and Edge on desktop, Safari on iPhone and Chrome on Android. Not tablets, watches, TV or desktop Safari.

What build do we hand mini?

An iOS simulator build, or an Android .apk, .apks or .aab (Play Asset Delivery works), uploaded from your CI or the Minitap CLI. Or connect your repository and mini builds each commit, monorepos included. Real iPhones, enabled per workspace, install your TestFlight builds.

How long does a run take?

Tests run in parallel, so run time depends on the size of your suite and how many devices and browsers your plan runs at once. A running test shows its estimate with a likely range. On a GitHub pull request, mini can run only the tests the change affects.

An AI agent sounds flaky. How do we trust a pass?

mini’s tests have no selectors or coordinates to go stale: it reads the screen on every run and checks the same acceptance criteria. Each criterion carries its evidence: what mini saw, a screenshot, the moment in the recording and its confidence. Every test ends Passed, Warning, Failed or Unprocessable. If mini can’t grade a test, because the build broke or sign-in failed, it’s marked Unprocessable.

Will it block our merges?

Only if you ask it to. The GitHub check informs by default. Turn on blocking for an app and a failing test fails the check, so branch protection can require it. In the GitHub Action, wait-for-result and fail-on-failure hold a deploy.

We’re not on GitHub. Does it still work?

Yes. GitLab, self-hosted GitLab and Bitbucket connect your repository, so mini builds from it and writes the suite from your code. Pull request comments and checks are GitHub only; any other pipeline starts runs and reads verdicts through the Minitap CLI.

Can we run it every night?

Yes. Schedule the whole suite, a tag or picked scenarios, on the latest build, a fixed build or a branch, and mini posts one Slack summary per run. Your CI or a release tag can start runs too.

What can’t mini test?

Face ID and fingerprint, NFC, Bluetooth, real SMS and calls, real payments, flows that finish in an external browser, and native tablet, watch and TV apps. In-app purchases run in Apple’s sandbox on a real iPhone or in a StoreKit test store, checkout uses a test card, and nobody is charged.

Bring your hardest flow.

Watch mini run your build, and keep the report.

Book a demoSee a real report