Importing Test Cases into Qtest from CSV: A Step‑by‑Step Guide
Learn how to import test cases into Qtest using a CSV file, including required headers, mapping rules, validation checks, and troubleshooting tips. Follow this concise guide to ensure a smooth import and quick verification.
28 May 2026, 18:52 UTC

Desired Outcome
Export a set of test cases from an external source and load them into Qtest’s Test Repository as fully‑functional test cases, with each step correctly ordered and all metadata preserved.
Prerequisites
CSV Format Requirements
Qtest’s CSV import recognises a limited set of column headers. Headers are case‑sensitive and must match exactly. The most common mandatory fields are:
| Header | Qtest Field | Notes |
|---|---|---|
| Test Case Name | Test case title | Required for new cases |
| Test Steps | Step description | Required for each step |
| Preconditions | Pre‑condition text | Optional, but useful |
| Step Number | Step sequence | Required for step ordering |
| Priority | Case priority | Optional |
| Owner | Case owner | Optional |
| Test Case ID | Existing ID (for updates) | Leave blank to create new |
All text must be UTF‑8 encoded. Avoid non‑ASCII characters that can break parsing. Line breaks inside cells should be escaped with double quotes (e.g., "Step description with\nline break").
Environment
- Qtest instance (v5.x or later) with Test Repository access.
- Browser with JavaScript enabled; the import wizard runs in the web UI.
- Spreadsheet editor (Excel, LibreOffice, Google Sheets) to clean and format the CSV.
Procedure
- Prepare the CSV file
- Open the spreadsheet editor and paste your data.
- Ensure the header row matches the table above.
- Remove any leading/trailing spaces and verify UTF‑8 encoding.
- Save the file as
test_cases.csv.
- Launch the Import Wizard
- Navigate to
Test Repository > Importin the Qtest UI. - Click
Upload CSVand select your file.
- Navigate to
- Map columns
- The wizard will auto‑detect headers. Verify each mapping; if a header is missing, click
Map Manuallyto choose the correct field. - Confirm that
Test Case IDis set toNewunless you intend to update existing cases.
- The wizard will auto‑detect headers. Verify each mapping; if a header is missing, click
- Validate and Import
- Click
Validate. Qtest will highlight rows with missing mandatory fields. - Correct any errors in the spreadsheet, re‑save, and re‑upload.
- When validation passes, click
Importto start the upload.
- Click
Validation Checks
- Rows missing
Test Case NameorTest Stepstrigger aValidation Errorand halt import. - Duplicate
Test Case IDvalues will update existing cases; verify IDs before running. - Large files (>10,000 rows) may time out; split into smaller batches if necessary.
- Case sensitivity: headers must match exactly; otherwise, columns may be ignored silently.
Recovery & Troubleshooting
- Import fails
- Check the
Import Activityfeed for error messages. - Review the CSV for malformed rows or unsupported characters.
- Use the
View Samplebutton in the wizard to see the parsed data.
- Check the
- Partial import
- Qtest imports all valid rows and logs failures. Inspect the log for skipped rows.
- Correct the problematic rows and re‑import only those rows.
- Existing ID conflict
- If you inadvertently include an ID that exists, Qtest updates that case. To avoid accidental overwrites, delete the
Test Case IDcolumn for new imports.
- If you inadvertently include an ID that exists, Qtest updates that case. To avoid accidental overwrites, delete the
Post‑Import Verification
- Open the
Test Repositoryand locate the newly created test cases by searching theTest Case Nameor by theImport Activitytimestamp. - Open one of the imported cases and expand the
Test Stepspane. Verify that steps are in numerical order and that the expected results match the CSV. - Run a quick execution of the test case to ensure all steps execute without errors.
- Check the
Activity Logfor the import record; the status should readSuccessand contain the number of cases imported.
Limitations & Best Practices
- Qtest does not support importing attachments or custom fields via CSV; use the API for those scenarios.
- Always keep a backup of the original CSV before editing.
- Use the sample template provided by Qtest (accessible from the Import Wizard) as a starting point.
- For large projects, consider splitting the import into modules (e.g., by feature area) to reduce risk of timeouts.
- After import, review the
Test Repositoryhierarchy to confirm that parent folders were created or matched correctly.
Example CSV Snippet
Test Case ID,Test Case Name,Step Number,Step Description,Expected Result,Preconditions,Priority,Owner
,,1,Open login page,Login page loads,NA,High,John Doe
,,2,Enter username,Username entered,NA,High,John Doe
,,3,Enter password,Password entered,NA,High,John Doe
,,4,Click login,Home page loads,NA,High,John Doe
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.