Skip to main content
Will it work for your app? Check the table, then the limits.

​
Platform by platform

Every ✅ is backed by a benchmark Mini passes on that platform. – means not yet. N/A means it doesn’t apply there.

​
Beyond the device

Signs in for you

Email and password, Sign in with Google, and phone sign-in with a static code.

Writes your suite

Connect GitHub and Mini drafts your stories and keeps them current.

Builds your app

Mini builds each commit, or you upload your own build.

Hands you the fix

Every failure comes with a video and a fix prompt for Cursor or Claude.

Flags what you didn't test

Suggestions catch visual regressions and broken navigation.

Drives several devices at once

Nothing stops Mini from waking up 3 devices together to validate a scenario that needs them live at the same time, like a chat between two accounts or a sign-in that kicks out another session.

Runs where you work

CI, the dashboard, Slack and the CLI.

​
Automate it with the CLI

Every command takes --json and returns stable exit codes. The GitHub Action wraps the same commands and posts a PR check.

​
What Mini can’t do today

A criterion that needs one of these comes back unprocessable, not as a bug in your app.
  • Backend checks. No database, server-log or analytics checks.
  • Other inboxes. Only @qa.minitap.ai test inboxes.
  • Real SMS or calls. Use a static code instead.
  • Biometrics, NFC, Bluetooth (iOS, Android). No Face ID, fingerprint or pairing.
  • Hearing the app (iOS, Android). Device sound isn’t captured.
  • Network toggling (iOS). No Wi-Fi or airplane mode.
  • Rotation and location (Web). Fixed viewport, no location mocking.
  • Wearables. No watches or paired devices.
  • Real money. Test and sandbox payments only.
  • Precise timing. Order and outcome, not latency.
Also out of scope: motion sensors, hardware buttons, flows that stay in an external browser, VPN setup, mocked network calls, changing the device clock, and watch or TV apps.

​
Native cloud tablets

Coming soon. Native cloud tablet runs for iOS and Android are pending, not deployed, and gated by native-tablets, which is off by default. Existing native runs continue to use phones.
The pending V1 supports one form factor per native platform in a run: phone or tablet, not both on the same platform. This does not add tablet targets for web, mobile-web, physical devices, or edge devices. See Triggering a run for the target contract. An iPhone-only build running on an iPad in scaled compatibility mode warrants a warning, not proof that the app supports an iPad layout. Unknown tablet compatibility does not count as supported.

​
Coming soon

  • Scheduled runs. Until then, push a tag on a schedule from a GitHub Action.
  • @mini retry in Slack. Until then, use Re-run in the dashboard.

​
Not on the roadmap

Unit and integration tests, load testing, security testing, and general-purpose automation. Missing something? Ask us. The roadmap moves fast.