> ## Documentation Index
> Fetch the complete documentation index at: https://www.minitap.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Import your existing tests

> Turn your test plan into scenarios, with your wording, test values and case IDs kept, during onboarding or at any time from the chat.

If your team already has a test plan, Mini starts from it. Hand Mini the file and it turns every case into scenarios you can run, keeping your case IDs, your test values and your expected results as written. This page covers the formats, what Mini keeps and what it adapts, and how to check that every case made it.

## Hand over the file

> [tab] When you add an app
>
> The setup asks **Do you already have tests?** Click **Import your tests** and pick your files: a zip, a CSV export, Markdown or a PDF. Mini reads them before its [first exploration](https://www.minitap.ai/docs/minitest/suite/exploration.md) and starts your suite from them.

> [tab] In the chat, any time
>
> Open **Ask Mini**, or a Workbench draft with **Draft a change**, attach the file with the paperclip or drop it on the chat, and ask Mini to import it:
>
> ```text theme={"theme":{"light":"github-light","dark":"vesper"}}
> Import the test cases from the attached file.
> ```
>
> Asking for the import is the approval, so Mini creates every scenario in the same turn. If you only share the file without asking, Mini proposes the import first and waits for your go.

You can also paste a list of cases straight into the message. Mini takes the pasted list as the scope, the same way it takes a file.

## Formats and limits

| You have | What to send |
| - | - |
| A spreadsheet | `.xlsx`, `.xls`, `.csv` or `.tsv` |
| A document | `.docx`, `.txt` or `.md` |
| Several files, or a folder of tests | A `.zip` of them. Mini unpacks it, up to 2,000 files and 50 MB once unpacked. |

Each file you attach in the chat can be up to 10 MB. For a bigger spreadsheet, attach a smaller file or paste the rows you want into the chat. If a spreadsheet can't be read, save it again as `.xlsx` or CSV and attach the new file.

In a spreadsheet, the header doesn't have to be on the first row, and every sheet is read. A Word document is read paragraph by paragraph and table row by table row.

## What Mini keeps as written

| From your case | Where it ends up |
| - | - |
| **Case ID** (`SM-112`, `PROJ-481`, a TestRail `C1234`) | The scenario name, each criterion it produced, and the description |
| **Test values**: the search term, product, coupon, amount, address | The criterion, quoted in your file's own language: `search for 'nutella'` |
| **Expected result**, including negative ones like "must not be found" | The criterion's outcome, as strict as your file |
| **Preconditions**: signed in, address set, item in the cart | The scenario's starting point and its [test account](https://www.minitap.ai/docs/minitest/setup/test-accounts.md) |
| The platform, account or role a case names | The scenario's platforms and test account, or a question for you when Mini has no account for it yet |

Your steps get rewritten into a description and acceptance criteria, because Mini decides on the spot how to move through the app. The values inside the steps don't change.

When something in a case can't stay as written, Mini says so in its report:

* **A value likely to change**, like a price or today's date: Mini keeps it, warns you it will go stale, and suggests a stable alternative.
* **A password or code written in the case**: Mini moves it to the test account and says so.
* **Something Mini can't do or observe on a device**: the case is listed as skipped, with the reason.

## How cases become scenarios

A test plan usually has one case per row, while a scenario covers one journey a tester walks in one session with one test account. So Mini groups related cases into one scenario, and each case keeps at least one criterion of its own, so a failure still points to one case ID:

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
[SM-112, SM-113] Search the catalogue by product name

1. [SM-112] Search for 'nutella' and confirm no 'nutella' product appears in the results
2. The no-result state shows a message
3. [SM-113] Search for 'diş macunu' and confirm matching products appear in the results

Source cases: SM-112, SM-113 (regression_suite.xlsx)
```

The criterion without an ID is one Mini added because the scenario makes it cheap to check. Mini lists its additions separately, so you can turn them down. A row with no ID is traced by its place in the file, like `Sheet1!A4`.

When a case is already partly covered, Mini extends that scenario with the case's criteria and adds its ID. Import the same file again later and Mini updates the scenarios that carry those IDs, without creating duplicates.

## Check that every case made it

Mini's report accounts for every case in your file: the scenario that carries it, or the reason it isn't there. When the file announces more cases than it holds, Mini says so.

In a Workbench draft, the **Source cases** tab lists each case with its **Ref**, **Title** and **Outcome**: **Added**, **Already covered**, **Skipped** or **Looks like an app bug**. Click a scenario in the list to open it.

New scenarios are drafts until Mini has checked them on a device. Nothing you imported runs in your suite before that check. See [Workbench](https://www.minitap.ai/docs/minitest/suite/workbench.md).

## From another Minitap app

To reuse scenarios you already have in this workspace, go to **Tests → New test → From another app**, pick the app, then the scenarios. Their acceptance criteria come along.

## Next steps

> [card] [Ask Mini](https://www.minitap.ai/docs/minitest/get-started/working-with-mini.md)
>
> What else to ask in the chat, and what Mini asks your OK for.

> [card] [Workbench](https://www.minitap.ai/docs/minitest/suite/workbench.md)
>
> Where imported scenarios are checked before they go live.

> [card] [What a scenario is](https://www.minitap.ai/docs/minitest/suite/anatomy.md)
>
> The shape every imported case ends up in.

> [card] [Test accounts](https://www.minitap.ai/docs/minitest/setup/test-accounts.md)
>
> Give Mini the accounts your cases sign in with.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.