Skip to main content
You can ask Mini for most things in plain language from the chat in the dashboard: write a scenario, import your test plan, change criteria, explain a result. This page covers what happens after you hit send.

​
Mini proposes, you confirm

For anything that changes your suite or uses device time, Mini first tells you what it’s about to do in a sentence or two and waits for your answer. You’ll usually see buttons like Yes, do it to confirm. If it needs something it doesn’t have, like an account or a test value, it asks for that too. Some requests are already the confirmation, so Mini goes ahead right away:
  • You ask Mini to import your test cases.
  • You open New scenario → Ask Mini and describe what someone should be able to do.
A few things Mini never does on its own:
  • Starting a run. You start runs yourself with Run tests, or from CI, Slack, or the CLI. See Triggering a run.
  • Irreversible actions in your app. Mini won’t place an order or make a booking during a test unless you’ve said that’s what the scenario should do.
  • Calling a scenario ready. A scenario is only ready after Mini has checked it on a device (see below).

​
From a request to a scenario

When you describe a goal, like “on Android, search for a phone and turn on the filter switch”, Mini turns it into a scenario with acceptance criteria. There’s no one-off test that disappears afterwards: what you ask for becomes part of what Mini can run again. A new scenario isn’t ready straight away. Mini first walks it on a device to make sure it can actually be tested: the screens exist, the accounts work, the criteria can be observed. Only then does it count as ready for your runs. See Drafts.

​
Importing your test plan

Attach your existing test cases to the chat and ask Mini to import them. Mini reads:
  • Spreadsheets: .xlsx, .xls, .csv, .tsv
  • Documents: .docx, .txt, .md
  • A .zip containing any of the above
Files can be up to 10 MB each. Mini keeps your wording, test values, and expected results as they are, and keeps your case IDs on the scenarios and criteria it creates, so you can trace every scenario back to your plan. Related cases are grouped into one scenario when that makes sense. At the end, Mini reports what happened to every case: added, already covered, skipped (for example, something that can’t be automated), or looks like an app bug.

​
Drafts: change, check, merge

Bigger changes happen in a draft, a copy of your suite where Mini can work without touching what your runs use. Your live suite doesn’t change until the draft is merged.
  1. Change. You and Mini edit scenarios in the draft. Mini may explore the app on a device to understand a screen before it writes.
  2. Check. Mini runs every changed scenario on a device against your latest build. If a scenario fails because it asks for the wrong thing, Mini fixes the scenario and checks it again. If it looks like your app is at fault, Mini tells you.
  3. Merge. Once every scenario is proven on a device, click Merge into suite. Your next run uses the new versions.
Drafts you open yourself always wait for you to merge. Drafts Mini opens to keep your suite up to date can merge on their own once everything is proven, unless they remove something or found a bug in your app. See Mini maintains your suite.

​
Platforms

Mini tests iOS, Android, and web apps. Most abilities work everywhere, and a few depend on the platform, like cookies on the web or offline mode on Android. See Capabilities for the full list.