Before you begin
You need permission to manage test cases in the Jira space. Updating a case also requires edit permission; creating a new version requires permission to create test case versions.
Prepare a CSV or Excel file.
For updates, include a Case Key column. Include Case Version when you want to update a specific existing version. Case Version is separate from Release Version.
Import your file
Open Vansah in your Jira space and go to Test Cases in the Test Repository.
Select Import and upload your file.
On Field Mapping, match the file columns to Vansah fields.
If you mapped Case Key, choose Create new test cases or Update existing test cases. Confirm your choice when prompted.
Select Next to review Columns Validation. Correct any blocking errors before continuing.
Start the import and review the Results for successful and failed cases.
You can go back to correct a mapping without starting over. If the file itself needs changes, edit it and select Change file. You can upload the corrected file using the same filename.
Column guide
Your spreadsheet headings do not have to match the names below. On Field Mapping, select the corresponding Vansah field for each column you want to import. Leave fields you do not need unmapped. For a case with multiple step rows, put case-level values on its first row.
Vansah field | How to fill it in | Example |
Required values |
|
|
Case Key | Existing test case key. Required for updates. For new cases, leave unmapped to generate a key, or provide an available key. |
|
Case Version | In update mode, enter the exact existing version to change. Leave blank to create a new version from the latest available version. This is the test case version, not a release. |
|
Headline | Test case title. Required when creating a case; up to 800 characters. | Verify account login |
Case Type | Use a Case Type configured for the project. For new cases, map this field or select a Case Type during validation. | Functional |
Case details |
|
|
Description | Describe the purpose and scope of the case. | Check a valid user login. |
Precondition | Describe the setup needed before execution. | User account exists. |
Test Case Status | Use a status configured for the project. | Draft |
Priority | Use an available Jira priority. | High |
Estimated Time | Enter a number of seconds, zero or greater. |
|
Assignee | Enter the user's Atlassian account ID, not their email address. | Atlassian account ID |
Owner | Enter the owner's Atlassian account ID. | Atlassian account ID |
Created By | Enter the creator's Atlassian account ID. | Atlassian account ID |
Labels and links |
|
|
Labels | Separate multiple labels with commas. Validation identifies labels that do not yet exist. |
|
Component | Use existing Jira component names; separate multiple names with commas. |
|
Link Requirement (Issue) | Enter Jira work item keys to link; separate multiple keys with commas. |
|
Link Requirement (Test Folder) | Enter a folder path including the project key and a trailing slash. Separate multiple paths with commas. |
|
Link Test Case(s) | Enter existing test case keys to link; separate multiple keys with commas. |
|
Test script |
|
|
Step | Enter one action per step row. Put additional steps for the same case on following rows. | Enter valid credentials. |
Test Data | Enter the input values for the corresponding step. | Valid username and password |
Expected Result | Enter the expected outcome for the corresponding step. | Dashboard opens. |
Plain Text | Enter a free-form test script instead of step-by-step instructions. | Sign in and verify the dashboard. |
Automation | Enter the automation script content. | Automation script |
BDD - Gerkin | Enter a BDD script using Given, When, and Then. |
|
Create new Test Cases
Choose Create new test cases to add cases to the repository. Provide a Headline and either map Case Type or select a Case Type during validation.
You may map Case Key to use keys from your file. Each key must be valid and available; an existing key cannot be used to create another case. Leave Case Key unmapped when you want Vansah to generate keys.
Update existing Test Cases
Choose Update existing test cases and map Case Key to identify each case.
Case Version in the file | What Vansah does |
An existing version, such as | Updates that exact version. |
Blank or unmapped | Creates a new version from the latest available version, then applies the imported data. |
Vansah reports a missing case key or a version that does not exist as an error. It does not substitute another case or version. Fields you leave unspecified are preserved. If you import test script content, it replaces the corresponding script content on the version being updated.
Tip: To change a particular version without creating another one, map both Case Key and Case Version, and fill them in for that case.
Importing test steps
A case with several steps can occupy several rows. Put the case details, including its Case Key and Case Version when updating, on the first row. Use the following rows for its additional steps. You do not need to repeat the headline and other case details on every step row. A case can also be imported without steps.
Fixing import errors
Columns Validation shows field and row errors before import. Check that keys and versions exist when updating, required values are present when creating, and mapped values such as Case Type and Test Case Status are valid for the project.
The Results screen shows what happened to each case. An import can succeed for some cases and fail for others, so review the individual outcomes before retrying. If a new version was created before a later operation failed, use the version identified in the error when retrying; otherwise, leaving Case Version blank could create another version.