Skip to main content
You give Mini a URL or a repository, a few accounts and some context. Mini opens your site in a browser, explores it, writes the scenarios, checks each one and runs your first regression. This page walks through that path for a web app, in the order the dashboard shows it. Testing an iOS or Android app? Follow the mobile quickstart.
Minitap is invite-only for now. Book a call and we’ll send your invitation after a short walkthrough.
1

Accept your invitation

Open the invitation email, sign in, and click Get started on the welcome screen. Your workspace is already created; you land straight in the setup.
2

Connect your code and your tools

Three optional screens, each with a Set up later button:
  • Your repository on GitHub, GitLab or Bitbucket. For a web app, Mini builds and serves each commit it tests, so you don’t need a deployed URL, and it posts a check on your pull requests. See GitHub.
  • Slack, for live run updates in a channel and runs started from a message. See Mini in Slack.
  • Jira and Confluence, Linear or Notion, so Mini reads your tickets and docs and files what it finds in your tracker.
You can connect any of them later from Settings → Integrations.
3

Tell Mini about your app

Let’s get Mini ready is a short conversation. For a web app, Mini asks for:
  • The app: a name, and Web app as its kind.
  • Where people open it: pick the devices and browsers your users have, and Mini tests the same ones. You need at least one.
  • Your repository, if you didn’t connect it earlier. With a repository, Mini builds every commit itself.
  • The URL to open, when there’s no repository: your production site, a staging host or any address Mini can reach.
  • Test accounts, one per kind of user Mini should sign in as. Pick My app has no sign-in if there’s nothing to sign in to.
  • Context about your product: specs, designs, boards. Documents work too.
  • Your existing tests, if you have any. Upload a zip, a CSV export, Markdown or a PDF and Mini starts from there.
  • Files your scenarios upload, like a photo or a document.
Skip anything you don’t have yet. Mini asks again later when it needs it.
4

Mini explores your app

Mini opens your site in a browser and walks through it page by page. You can watch it live. When it’s done, it shows you the map of screens it found and asks Happy with the map?
5

Review the scenarios

From the map and everything you shared, Mini drafts the scenarios worth running, each with its acceptance criteria. Every draft is checked in a browser before it counts as ready. If Mini hits something it can’t guess, like a missing account or an ambiguous expected result, it asks you in the chat.
6

Run your first regression

Click Approve & run first regression. If a few questions are still open, Skip & run starts the scenarios that are ready now and keeps the others as drafts until you answer.

​
Browsers you can pick

Each browser you pick becomes a default target for the app’s runs. You can change the list later and pick other targets for a single run. See Web apps.

​
What you get back

A run report: a verdict for every scenario and browser, the recording of the session, and for each failure the criterion that broke, the logs and a fix prompt ready for Cursor or Claude.

​
Next steps

Test staging and preview URLs

Point a run at a preview deployment and pick browsers per run.

Reach a private site

For a site behind a firewall, a VPN or a country restriction.

Run on every pull request

Add the GitHub Action so each PR gets a verdict before it merges.

Read a run report

What each verdict means and how to act on a failure.