Page History
...
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):
Info | ||
---|---|---|
| ||
If you choose the “,” (comma) as the CSV column separator, then you must use quotation marks around any field that contains commas. |
...
- Log in with an administrator account.
- Go to System > Import and Export > External System Import.
- Select the Xray Test Case Importer.
- Follow the Setup Page section instructions
...
- Log in with a non-administrator account.
- Got to Tests menu > Test Case Importer as shown in the image
- Select the Test Case Importer menu item
- Follow the Setup Page section instructions
...
Provide the basic settings for the importation process.
- The CSV Delimiter field is the column delimiter used in your CSV source file.
- The File Encoding field is the encoding used in your CSV source file.
- Optionally, you can use the settings from a previous importation.
...
- Select the Xray project where you want your Manual Test cases to be imported.
- Set the Date formats that will be used for all Jira custom fields and also to the Manual Test Step Custom fields of type "Date picker" and "DateTime picker".
Field Mapping Page
Map the fields from your CSV to Jira and Xray fields
It is mandatory to map at least three fields:
...
Info | ||
---|---|---|
| ||
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.
Info | ||
---|---|---|
| ||
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. |
...
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.
Info | ||
---|---|---|
| ||
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. |
...
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.
Links
You can import a link to other issues for newly-created Tests by choosing the "Link ..." mapping.
...
Info | ||
---|---|---|
| ||
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. |
Date Time fields
...
As in Jira's native CSV import, we provide means to updating an existing issue.
In order to Update an issue you must comply with the following pre-conditions:
...