Page History
...
Here is an example of test cases structure:
And here is how the CSV file looks like once the test cases above are exported to CSV:
| Info | ||
|---|---|---|
| ||
If you choose the “,” (comma) as the CSV columns separator, you must quote any field that contains commas. |
...
For any questions regarding this feature, please contact our support team.
...
Special fields
Attachments
...
| title | Attachments |
|---|
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. |
...
| 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", " 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 be seen within the "Orphans" meta-folder. |
Links
You can import link to other issues, for the newly created Tests by choosing the "Link ..." mapping.
| Info | ||
|---|---|---|
| ||
Whenever importing Tests, it's also possible to 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.
|
...
| Info |
|---|
| Issue |
Comments
Comments can be added to Test issues, using the following
...
syntax "DateTime;User;CommentBody
...
" ,where DateTime and User are optional.
DateTime uses the Date format given on project mapping page, and User
...
must be a valid username.
| Info | ||
|---|---|---|
| ||
: "01/01/2012 10:10;Admin; This comment works" |
...
Useful tips for importing Tests
Importing data in any system may be a non-linear process and you may need to run it multiple times until you got the expected result, because simple things such as forgetting to map a field may happen.
...
- add a unique label to all your tests, so you can clearly identify the tests imported at a given time; that will make your analysis simpler and eventualy if you do some bulk operation in them (e.g. change fields, remove them) it also be easier;
- use a custom field for storing the external ID of the tests in their original system. Thus, whenever tests are imported, you can easily compare them with the original ones in the original system;
...