If you're migrating from a spreadsheet or another tool, you can import test cases in bulk using a CSV file rather than entering them one by one. The import maps CSV columns to test case fields and creates the cases in a single operation.
Imports are project-scoped — you import into a specific project, and the test cases appear in that project's Test Cases section.
Always start from the official template to avoid column mismatch errors:
| Column | Required? | Notes |
|---|---|---|
| Title | Required | Short name of the test case |
| Description | Optional | Context or background for the test |
| Preconditions | Optional | State the system must be in before testing |
| Steps | Required | Test steps separated by a pipe character ( | ) |
| Expected Result | Required | What a passing result looks like |
| Priority | Optional | High / Medium / Low — defaults to Medium if blank |
| Suite | Optional | Suite name to add the test case to. Created automatically if it doesn't exist |
| Tags | Optional | Comma-separated tag list |
Imported test cases land in the project's All Test Cases list. If you specified a Suite column, each case is also added to the named suite (created automatically if it doesn't exist).
Links to stories are not created during import — you'll need to add those after import, either by opening individual test cases or using the story detail view's Test Cases tab. Establishing these links is important for coverage reporting.
The import fails with a "missing required column" error
The CSV must have exactly the column headers shown in the template — spelling and capitalisation matter. Download the template from the import dialog and use it as your starting point rather than building a CSV from scratch.
Steps are all ending up in one cell
Steps must be separated by a pipe character ( | ) within a single cell. If your steps are in separate rows, they won't be recognised. Use the template to see the expected format before importing.
My test cases imported but the Suite column was ignored
Suite names are case-sensitive. If the suite already exists, the name must match exactly. Check the existing suite names before importing, or import first and then move cases manually.
I get a "duplicate title" warning
Silverile detects test cases with identical titles in the same project. You can choose to skip duplicates (keep the existing case) or import anyway (creates a second case with the same title). For large imports, review and de-duplicate the CSV first.
The import limit is preventing a bulk upload
Imports are limited to 500 test cases per file. For larger sets, split your CSV into batches of 500 and import sequentially.