Import test case results from a CSV file into Vansah, including overall outcomes, individual test step results and results for an existing Test Plan iteration.
Choose a template below, replace the sample values with your testing information, then upload the file and review its field mappings before importing.
Before you start
You need the Import Test Case Results permission in Vansah. For plan imports, you also need this permission in the plan’s Jira space.
Confirm you can access the spaces, cases and requirements referenced in your file.
For plan imports, the plan and iteration must already exist. The requirement must belong to that plan, and the case must be linked to that requirement within the plan. Blocked cases or requirements cannot receive these plan results.
For step imports, the case must already contain a multi-step script. Use its actual step numbers.
Use result names enabled in your Vansah configuration. The examples use
PassedandFailed.Keep the CSV header row. Save your edited copy as CSV; the current upload limit is 5 MB.
Overall test case results
Template
Column | How to fill it in |
| An existing Vansah case key, for example |
| The Jira work item key or test folder path the case was tested against. For example, |
| The overall outcome. Map this column to Test Case Result. It is required when step results are not supplied. |
Use one row for each case-and-requirement result. A case key identifies the case; the tested requirement identifies its execution context. They are separate values, so do not replace one with the other.
For folder requirements, use Copy Folder Path in Vansah to obtain the space-qualified path.
Individual test step results
Template
Start each case with a row containing its Case Key and Tested Requirement.
Put the first step on that row. Place subsequent steps immediately underneath, leaving the case-level columns blank as shown. These continuation rows belong to the preceding case record. Start a new case with a new populated Case Key.
Additional column | Meaning |
| In this template, the Jira release name, such as |
| The execution environment name, such as |
| The Jira sprint name, such as |
| The existing script step to receive the result. |
| What happened during that step. This records an observation; it does not replace the script's expected result. |
| The outcome of the numbered step. Map both this and |
| An optional explicit case-level outcome when step results are supplied. The sample leaves it blank so the case outcome is calculated from its step results. |
Check the Version column: The supplied step-results template uses Version for a Jira release. A test case export may use Version for the case revision instead. Check the values before mapping; leave case revision columns as None when importing results.
Keep each case's steps together. Do not sort the step rows independently, put a continuation row before its case, or use a step number that does not exist in the script.
Results for a Test Plan iteration
Template
Additional column | How to fill it in |
| An existing plan key, such as |
| An existing positive iteration number, such as |
Iteration requires Test Plan Key; it cannot select an iteration on its own. The import does not create a missing plan, requirement link or iteration.
The sample uses a relative folder path within the plan. A space-qualified path such as PREM/regression/address/verification/ is also supported. Prefer the path copied from Vansah when preparing your own file.
Optional columns you can add
The importer also supports the following fields beyond the columns already included in a template:
Column | Guidance |
| Use |
| Use the tester’s Jira account ID. The importer also recognises the Tester ID header used in Vansah exports. If omitted or blank, the current user is used. |
Actual Time | Time spent in whole minutes, from 0 to 14,400. Values such as 15 or an exported value such as 15m are accepted. Put this value on the case’s first row. A positive value adds a time log to the Test Run for the tester; 0 adds no time log. |
You can add the release, environment, sprint or comment columns to a case-level file when needed. Map only the columns you intend to import. Plan keys and iterations can also accompany step results: put them on each case's first row, rather than on its blank-key continuation rows.
Import the completed file
In your Jira space, open Vansah. Select the Settings cog on the Vansah Board, then Import Test Case Results.
On Setup, upload your completed CSV, then select Next.
On Field Mapping, match the file columns on the left to the Vansah fields on the right. Map Result to Test Case Result. Map step results, plan fields and optional columns only when you want to import them; choose None for unused columns. Check Release Version carefully if your file has a Version column.
Select Next to open Columns Validation. Vansah checks the file and its import targets. Expand any field showing errors to see which rows need attention. Use Back to correct the mapping, or update and upload the CSV again as needed.
When validation succeeds, select Next to start importing. Wait for the import to finish.
On Results, review the Successful and Failures and warnings sections. Check the execution in the intended work item, Test Folder or plan iteration. If some records failed, prepare a corrected file containing only the records that still need importing.
After a completed import, you can choose to import another file. Review the completed results first so you do not import successful records again.
Common checks
Problem | Check |
Case not found | Replace the sample key with an existing accessible Vansah case key. |
Requirement not found or not part of the plan | Check the work item key or copied folder path, then verify the plan's linked requirements. |
Case is not linked to the plan requirement | Link the case under that specific requirement in the plan before importing its result. |
Invalid result | Use an enabled Vansah result name; do not substitute an abbreviation that is not configured. |
Invalid iteration | Use an existing whole-number iteration, or leave it blank to use the latest. |
Step results are attached to the wrong case | Restore the case header row and keep its continuation rows immediately below it. |
Unexpected column mapping | Review the destination for each CSV column. In particular, check Release Version, Test Case Result, Test Step Result and Actual Time. |