How import works

If the client already wrote the tests, do not retype them. Open the project, choose Import tests (or Import in the project), then pick the workflow that matches the files you have. You always review, then apply. Nothing becomes suites and cases until you confirm the preview.

​

Which door to use

Both land as normal project suites and cases. After apply you edit, run, and deliver them like anything you typed by hand.

​

What happens on the Import page

1. Open the project and go to Import.
2. Choose Smart Matrix Import or Unified Smart Import.
3. Upload the file (or files).
4. Map or review what the importer found: suites, cases, steps, personas, cycles when those exist in the source.
5. Fix anything wrong in the preview. If the preview is junk, fix the file and start again. Do not apply a bad preview.
6. Apply. Then create a cycle and run the work.

​

What import is not

• From my codebase is a different path. That uploads simpleuat-project-setup.json from an agent. It is not the same as pasting a Word spec. Codebase setup.
• Test Suite Packs install a reusable checklist. Use a pack when you do not have a client file. Packs.
• Import does not replace a run. After cases exist, you still execute them in a cycle.

​

Plans and permission

Some workspaces hide an importer, or show Upgrade required, until the plan includes import. You also need import permission on the project. If you see a lock, ask the project manager or upgrade at Settings > Billing.

​

After you apply

There is no undo for apply. Duplicate imports can create duplicate cases. Deprecate or delete extras. Column meanings: spreadsheet mapping. If the preview looks wrong: import problems.