Importing Test Case Results | Vansah Help Center

Before you start

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 Passed and Failed.
Keep the CSV header row. Save your edited copy as CSV; the current upload limit is 5 MB.

1. Overall Test Case results

Template

Column	How to fill it in
`Case Key`	An existing Vansah case key, for example `MYD3-C211`.
`Tested Requirement`	The Jira work item key or test folder path the case was tested against. For example, `MYPRJ-1` or `MYPRJ/folder1/folder2`.
`Result`	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.

2. Individual test step results

Template

Test Case Results With Steps

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
`Version`	The Jira release name, such as `R1.1`. This is not the test case revision number.
`Environment`	The execution environment name, such as `UAT` or `SYS`.
`Sprint`	The Jira sprint name, such as `Sprint 1`.
`Test Step Number`	The existing script step to receive the result.
`Actual Test Comment`	What happened during that step. This records an observation; it does not replace the script's expected result.
`Test Step Result`	The outcome of the numbered step. Map both this and `Test Step Number` when importing step outcomes.
`Result`	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.

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.

3. Results for a Test Plan iteration

Template

Test Case Results for a Test Plan

Additional column	How to fill it in
`Test Plan Key`	An existing plan key, such as `PREM-P1`. Once this column is mapped, every case record needs a plan key.
`Iteration`	An existing positive iteration number, such as `1` or `2`. Use the number, not text such as `Iteration 1`. Leave it blank or unmapped to target the plan's latest iteration.

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
`Tested Date`	Use `MM/DD/YYYY` or `M/DD/YYYY`. An omitted value uses the current date. Do not supply a future date.
`Tested By`	Use a Jira account ID, rather than a display name or email address. If omitted, the current user is used.

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 > Settings > Import Test Case Results.
Upload the CSV on Setup.
On Field Mapping, review the detected mappings. In particular, map Result to Test Case Result and retain the separate mappings for step results and plan fields where applicable.
Run Columns Validation. Correct the reported rows, including missing keys, invalid outcomes, unavailable plan iterations or incorrect requirement membership.
Continue with the import once validation succeeds.
Review Results, then check the imported execution in the intended requirement or plan iteration. If rows fail, check which rows succeeded before submitting a corrected file again.

These navigation steps follow the Vansah import guide; the mapping names above match the supplied templates and current importer fields.

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, especially `Version`, `Result`, and `Test Step Result`.