You can use the Xray's Test Case Importer (a Jira Importer Plugin extension) to import Manual Tests from a CSV source file.
The CSV source file must follow some simple rules.
You can name the fields as you wish since they are going to be mapped during the importation process, but there are three mandatory fields:
Here is an example of test cases structure:
This is how the CSV file looks like once the test cases above are exported (download it from the downloadable examples section):
If you choose the “,” (comma) as the CSV column separator, then you must use quotation marks around any field that contains commas. |
If you need to use new lines within a field, for example, in the issue description, then you need to quote the field. |
It is now also possible to import test cases as a non-administrator JIRA user. Please follow the described steps in order to use this feature |
For demonstration purposes, the CSV example file from the previous section is used.
To complete the importation process, follow the steps below.
Only users that have the Bulk Change permission will have this option available. The configuration can be found in the Jira Administration / System. Additionally the user will only be able to import data into projects where he has the Create Issues permission. |
Provide the basic settings for the importation process.
Select the Xray project where you want your Manual Test cases to be imported.
Map the fields from your CSV to Jira and Xray fields
It is mandatory to map at least three fields:
The fields that are not mapped will not be imported to the test case.
Only custom fields that have the issue type Test selected as one of the applicable issue types will be available for mapping. Available custom fields for import:
Note: Only "single-value" custom fields are supported. "Select List (cascading)" custom fields behave as a single-value field; in that case, you have to specify the value in the format "parent -> child" as mentioned also for Jira's native CSV importer. |
Map the CSV column values. In the example above, the Map Field Value checkbox is selected for Priority, so those values are going to be mapped.
Now just click Begin Import and Xray Test Case Importer will import the manual test cases to the selected project.
The importation process is complete. A configuration file can be saved to import other manual test cases in the future.
It is possible to attach files to Test and to Test Steps.
The attachment may be referred by name (in this case the file:// protocol is assumed), by "file://" or "http(s)://". Multiple files may be specified within one CSV column; for this, the attachments must be delimited by space. Note: For file protocol, only files in the "<JIRA_DATA_HOME>/import/attachments" folder will be imported. |
If you want to add the Tests to some folder within the Test Repository, you can specify a column having the Test Repository Path.
Folders and their respective sub-folders must be delimited by "/", as shown in the following example:
During the mapping step, you need to map the CSV column containing the path to the "Test Repository Path" Xray's custom field.
The "Test Repository Path" is case insensitive and each folder is trimmed (spaces are removed from the start/end of it). This means that "components/compA", "components /compA", and " components/COMPA" are all the same and will be mapped to the same folder within the Test Repository. If the folder is not found, then the Test is created, but it is not associated with any folder; it will appear in the "Orphans" meta-folder. Unless you selected the option 'Create Folders', in the Setup page. |
To create new folders and sub-folders, in case they do not exist in the Test Repository, you must select the option 'Create Folders' in the Setup page of the Test Case importer.
Make sure you have the Hierarchical Test Organization enabled and the logged in user belongs to a Project Role allowed to edit the Test Repository. You can check this settings under the Xray Global Settings.
You can import a link to other issues for newly-created Tests by choosing the "Link ..." mapping.
When importing Tests, you can specify the links to the requirements that each Test validates. For that purpose, columns must be mapped as Link "Tests". If the Test covers multiple requirements, then multiple CSV columns must be used, each one being mapped in the same way. |
Dates and Date Time field formats must comply with the Java SimpleDateFormat. On the project mapping page, the format used on the CSV file should be given in order for the import process to complete without errors or warnings.
|
Comments can be added to Test issues using the "DateTime;User;CommentBody" syntax, where DateTime and User are optional.
More that one comment can be added for each issue, by adding more than one column on the CSV file.
DateTime uses the Date Time format specified on the project mapping page, and User must be a valid username.
|
An issue's priority defines its importance in relation to other issues. You can read more here. Before Jira 7.6, priorities could only be defined globally (i.e, for all projects). In Jira 7.6, Jira allowed a Project to have custom Priority Scheme. When using Jira CSV importer, Jira has different behaviors when Priorities are provided or not, depending on the Jira versions.
Xray will have the same behavior, no matter what version of Jira. When a user (admin or not) is trying to import a CSV with Xray Test Case Importer:
Importing data in any system is a non-linear process; you may need to run it multiple times until you get the expected result because it is easy to forget to map a field or use a delimiter, etc.