Test Case Import
Currently the add-on supports to import/migrate Test Cases from below:
[Screenshot - UG870_Admin_Test_Case_Import01]
Points to remember while importing Test Cases:
- Summary is mandatory to start the import.
- Appropriate date format is required when processing with date fields.
- Use the syntax that complies with the Java SimpleDateFormat
- Example: set date format to yyyy-MM-dd h:mm a if you are going to import date time value as 2030-01-01 12:00 AM
- Step ID is mandatory when a step is provided.
- Providing ISSUE KEY will update the corresponding issue, if found.
- Specify Requirement ID in Requirement column if you want to import Test Cases with Requirement associations.
Note: if Requirement ID specified in import file cannot be found in your project, the Test Case will still be imported without Requirement associations. - Specify Test Suite path in Test Suite column if you want to import Test Cases with Test Suite associations.
Note: If Test Suite path specified in import file cannot be found from your project, it will be created from import file. - At the end of the CSV file import wizard, you will be given the option of creating a CSV configuration file, which contains the settings you configured while running through the CSV file import wizard. This is useful if you need to test your CSV file import on a test JIRA server first before performing the import on a production system.
Import Test Cases from a .csv file:
To import test cases from .csv file, follow these steps:
- Click "Administration->Add-ons" from the main menu.
- Click the "Test Case Import" link from the left panel under the "synapseRT" section.
- Click "CSV" icon from the page.
- Choose a project from "Project" dropdown and click "Next" button.
- Click "Choose File" button, browse to your test case file (.csv format).
- Specify a "Delimiter" if necessary.
- Select "Use an existing configuration file" if you have, it will ask you to select the configuration file and mappings in the file will be loaded automatically in next page.
- Click "Next" button.
- Select the CSV fields to import, then set how you would like these converted to fields in JIRA.
- Note: the field mapping can be done automatically if you have a configuration file created in your previous import and follow step 6.
Click "Import" button.
Note:
If you need to import another CSV file with the same (or similar) settings to what you used through this procedure, click the save the configuration link to download a CSV configuration file, which you can use at the fifth step of the CSV file import wizard.
[Screenshot - UG870_Admin_Test_Case_Import02]
Tips for importing CSV data into JIRA fields
Below are some helpful tips when importing data from your CSV file into specific JIRA system fields and user created custom fields:
Jira Field | Import Notes |
---|---|
- | synapseRT import only supports Jira system field (e.g. Summary, Priority ...) and custom fields from Jira standard field types (e.g. Checkboxes, Date Picker ...) Jira advanced field types (e.g. Development Summary, Global Rank ...) and any field types from third party apps are not supported. |
Summary | This is the only required field. |
Issue Key | You can set the issue key for an imported issue. If an issue with a given key already exists in JIRA, it will be updated instead. |
Component(s) | You can import issues with multiple components by entering each component in a separate column. |
Affects Version(s) | You can import issues with multiple 'Affects Versions' by entering each version in a separate column. |
Fix Version(s) | You can import issues with multiple 'Fix Versions' by entering each version in a separate column. |
Due Date |
|
Labels | You can import issues with multiple labels by entering each component in a separate column. |
Epic Link | Provide Epic issue key if you want to link issues to an existing Epic in Jira. |
Custom field types:
|
|
Custom field types:
|
Example:
|
Custom field types:
|
|
Custom field type:
|
Example:
|
Custom field type:
|
|
Downloadable examples
- Total of three Test Cases along with folder structure (Test Suite) and several Jira standard fields, comma (,) delimited: Test Case Import Sample File.csv; field mapping file: Test Case Import Configuration.txt
- Total of three Test Cases along with folder structure (Test Suite) and all Jira standard custom fields, comma (,) delimited, date format set to dd/MMM/yy h:mm a: Test Case Import Sample File with Jira Standard Custom Fields.csv; field mapping file: Test Case Import with Jira Standard Custom Fields Configuration.txt
Import Test Cases from Test Link exported .xml file:
To import test cases from Test Link exported .xml file, follow these steps:
- Click "Administration->Add-ons" from the main menu.
- Click the "Test Case Import" link from the left panel under the "synapseRT" section.
- Click "Test Link" icon from the page.
- Choose a project from "Project" dropdown and click "Next" button.
- Click "Choose File" button, browse to your test case file (.xml format).
- Click "Next" button.
- Select the XML fields to import, then set how you would like these converted to fields in JIRA.
- Click "Import" button.
[Screenshot - UG870_Admin_Test_Case_Import03]
You can find test case import sample file (.xml) from the link: TestLink_Test_Case_Import_Sample_File.xml
Note:
In Test Link export file (.xml), only value IDs are present for some fields. If you want to import such fields to synapseRT, you need replace these IDs with actual values first from xml file, and then start your import process. Otherwise those fields' values will not be imported as synapseRT doesn't know what exactly they are.
Below are some samples to replace IDs with actual values in Test Link xml file:
Test Link Field | Field's Data in XML File | Update Sample |
---|---|---|
Version | <version><![CDATA[1]]></version> | <version><![CDATA[Version 1.0]]></version> |
Importance | <importance><![CDATA[2]]></importance> | <importance><![CDATA[High]]></importance> |
Execution Type | <execution_type><![CDATA[1]]></execution_type> | <execution_type><![CDATA[Manual]]></execution_type> |
Migrate Test Cases from Zephyr add-on:
synapseRT supports to migrate Zephyr Test Cases (issue type = Test) to synapseRT Test Cases (issue type = Test Case).
To migrate test cases from Zephyr add-on, follow these steps:
[Precondition]:
- Install synapeRT add-on to JIRA server from which Zephyr Test Cases are created.
- Disable Zephyr add-on, please refer to Atlassian Documentation about how to "Disabling and enabling add-ons".
- Bulk move Zephyr Test Cases from "Test" issue type to "Test Case" issue type, please refer to Atlassian Documentation about how to "Move multiple issues".
Note: you may need configure your JIRA project to make sure "Test Case" issue type is available for your project.
Once above preparation is done, follow below steps to complete data migration:
- Click "Administration->Add-ons" from the main menu.
- Click the "Test Case Import" link from the left panel under the "synapseRT" section.
- Click "Zephyr" icon from the page.
- Click "Import" button.