Importing Test Cases through a CSV or Excel file is a fast and efficient way to add multiple test cases into Vansah at once, eliminating the need to create each test case manually. This approach is especially useful for teams handling large test suites or transitioning from other testing tools.
If you are migrating test cases from another test management solution, Vansah’s importer makes the process seamless. It allows you to recreate your existing test cases in Vansah while preserving critical information from the original system.
The importer can retain key test properties such as the original Test Case key and automatically link test cases to existing Jira work items. Additionally, Test Folders are created automatically in Vansah, ensuring your test cases remain well-organized and aligned with your existing structure.
In this article, we’ll walk through a step-by-step guide on how to import test cases into Vansah using a CSV or Excel file, making your migration or bulk creation process simple and efficient.
Required Permissions
You can import Test Cases into a Jira project only if you have at least one of the following permissions:
ADMINISTER PROJECTS
BULK CHANGE
DELETE ISSUES
Download Template
A CSV delimited or XLSX file is required when importing data.
Please Note: inline CSS and Nested HTML elements will not be supported for Multi line (Text) fields.
Understanding Test Case fields
Field | Format | Description | Source | Required |
Test Case Key | Alphanumeric string | A unique identifier for each Test Case within the Jira project. This is essential for tracking and referencing. Provide a Test Case key example: MTR-C400 | Vansah | Optional |
Headline | Single Line (Text) | A brief, descriptive title for the test case. It should summarize the purpose of the test | Vansah | Mandatory |
Case Type | Single Line (Text) | Specifies the type of Test Case, such as functional, regression, or automation. The Test Case Type should be defined in your Vansah project settings. If the Type does not exist an error will be provided. | Vansah | Mandatory |
Precondition | Multi line (Text) | Any conditions or setup required before executing the test case | Vansah | Optional |
Description | Multi line (Text) | A detailed explanation of the test case, including its purpose and scope. | Vansah | Optional |
Owner Id | Alphanumeric (Jira Account ID) | The Jira Account ID of the person who person responsible for managing the test case. If not provided the user importing the Test Cases will become the Assignee. | Jira | Optional |
Assignee Id | Alphanumeric (Jira Account ID) | The Jira Account ID of the person who person responsible for executing the test case. If not provided the user importing the Test Cases will become the Assignee. | Jira | Optional |
Created By | Alphanumeric (Jira Account ID) | The Jira Account ID of the person who created the test case. If not provided the user importing the Test Cases will become the creator. | Jira | Optional |
Priority | Text | The priority level of the Test Case. If the Priority does not exist an error will be provided. | Jira | Optional |
Estimated Time | Numeric | An estimate of the time in seconds required to execute the test case | Vansah | Optional |
Test Case Status | Text | Indicates the current status of the test case, such as New, In Progress, or Completed. The Test Case Status should be defined in your Vansah project settings. | Vansah | Optional |
Labels | Comma-separated values | Tags or keywords associated with the test case for easier categorization and searching. If the Jira Label does not exist it will be created in Vansah. | Jira | Optional |
Components | Comma-separated values | This field allows you to specify the particular modules, features, or sections of the application that the Test Case is designed to test. If the component does not exist in Jira an error will be provided. | Jira | Optional |
Link Requirement (Issue) | Comma-separated values | References to any related Jira Issue Keys (requirements) that the Test Case should be linked to. Example: RD-3, RD-4, ABC-1 | Jira | Optional |
Link Requirement (Test Folder) | Comma-separated values | Links to the Vansah project Test Folder path where the Test Case is organized. Example: "Regression/Address/verification/cycle 1/"
If the path does not exist the importer will create in. | Vansah | Optional |
Link Test Cases | Test Case Key(s) Comma-separated values | Used to create relationships between different test cases. By linking test cases, you can manage dependencies between them, ensuring that prerequisite tests are executed in the correct order. | Vansah | Optional |
Step Id (Optional) | Numeric (Starting from 1) | A unique identifier for each step within the test case script. Each row should have a matching step id starting from 1 | Vansah | Optional |
Step | Multi line (Text) | Detailed instructions for executing each step of the test case. Mandatory if Step Id is provided | Vansah | Optional |
Test Data | Multi line (Text) | Specific data required to perform the test steps | Vansah | Optional |
Expected Result | Multi line (Text) | The anticipated outcome of the test case if all steps are executed correctly. | Vansah | Optional |
Plain Text | Multi line (Text) | You can use Plain Text to import a Test Case with Plain Text as a test script type. | Vansah | Optional |
Bdd-Gerkin | Multi New line (Text) | This field allows you to define test cases using Gherkin syntax as a test script type. BDD is a language used in to describe application behavior in a clear, structured format | Vansah | Optional |
Steps to Import Test Cases
Log in to Jira with an administrator account or a user with “Bulk Change permission“
Open your space and navigate to the Vansah Board.
On the right side of the Vansah Board, click the Gear (⚙️) icon to open Vansah Settings.
Select Import Test Cases.
Click Choose File and upload your CSV or Excel file containing test cases.
Click Next
On the Field Mapping screen, map file columns to the corresponding Vansah fields (for example: Headline, Description, Steps).
8. Click Next to validate all provided columns have been mapped appropriately.
In case of any changes, a user may choose to click Back button and change the given file.
9. Click Next to see the final Result.
A success message will be displayed.
