Importing Test Cases from CSV

If you're migrating from another tool or already keep test cases in a spreadsheet, you don't have to re-enter them one by one. Test cases → Import → Import from CSV lets you upload a CSV file and map its columns directly to DevAssure fields.

Starting an import

1. Go to Test cases.
2. Click Import (next to Add Test Case), then select Import from CSV.
3. Choose a CSV file from your machine. DevAssure parses it immediately and shows a summary — for example, "Found 18,992 test cases in Scenarios.csv" — so you can confirm it picked up the right file before mapping anything.

Mapping columns to fields

The import dialog shows a DevAssure Field → CSV Column table. For each field, choose which column in your CSV supplies that value:

DevAssure field	Required?	Notes
Title	Required	The test case name, as it will appear in the folder tree and session results.
Folder	Optional	See Folder paths below — folders are created automatically if they don't exist yet.
Priority	Optional	Maps to P0–P3 if your CSV has a priority/severity column.
Tags	Optional	Maps to a tags column for later filtering.
Steps	Required	See Mapping steps below — supports mapping more than one CSV column.

Fields marked (optional) have an info icon with a short explanation inline in the dialog — hover it if you're unsure what a field expects.

Folder paths

If your CSV has a column indicating where each test case should live (for example, a Module or Suite column), map it to Folder. Folder values should be / separated — a cell containing airbnb/checkout will file that test case under a checkout folder nested inside airbnb. Folders that don't already exist are created automatically during import; you don't need to pre-create the folder structure first.

If you leave Folder unmapped, imported test cases are placed at the root level, same as manually created ones with no folder selected.

Mapping steps

Unlike the other fields, Steps can map to more than one CSV column — use Add column... to bring in additional columns if your spreadsheet spreads steps across multiple columns (for example, Step 1, Step 2, Step 3 instead of one combined column). Mapped columns are combined in the order you add them to form the test case's ordered step list, the same plain-English format described in Test Cases.

If your CSV already has a single column with one instruction per line, map just that one column and skip Add column.

Running the import

Once every required field (Title, Steps) has a mapping, click Import. DevAssure creates a test case for each row, filing it into the mapped folder (creating folders as needed) and applying priority/tags where mapped. You can cancel out of the dialog at any point before clicking Import without creating anything.

Large files — the summary step will show counts in the tens of thousands — import in the background; the new test cases appear in the folder tree as they're created; no need to keep the dialog open.

After importing

Imported test cases behave exactly like manually created ones — they're editable, runnable, schedulable, and show up in History the same way. If a step didn't translate cleanly (for example, an ambiguous instruction from a legacy tool's export format), open the test case and refine the wording — see Writing good steps for guidance on phrasing steps so O2 executes them reliably.

Related

• Test Cases — authoring, folders, priority, and tags in detail.
• Test Data & Config — for values you'd rather reference than repeat across thousands of imported rows.