Document toolboxDocument toolbox

Test Case - Import and Export

TestRay supports importing multiple test cases via CSV format, it helps when migrating existing test cases you might have in Excel or other test management tools. 

As per Jira’s design, to ensure add-on have proper permission to complete issue import, the atlassian-addons-project-access role will be assigned to all of the permissions in project scheme automatically. Please DON’T remove it from project scheme, otherwise import will be failed due to lack of permission.

Import Test Cases to a Jira project

Launch a Jira project and then navigate to 'Tests->Test Suites->Import Test Cases TAB', following the steps in the page to complete your import.

Points to remember while importing Test Cases

  1. Summary is mandatory to start the import.

  2. 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

  3. Step ID is mandatory when a step is provided.

  4. Providing ISSUE KEY will update the corresponding issue, if found. Existing Test Steps will be replaced by the ones in CSV file.

  5. Specify test suite path in Test Suite column if you want to import test cases with test suite associations.

    1. If test suite path specified in import file cannot be found from your project, it will be created from import file.

    2. You can import test cases with multiple test suites by entering each test suite in a separate column.

  6. Specify requirement issue key if you want to link test case to existing requirement issue during the import.

    1. You can import test cases with multiple requirement links by entering each requirement key in a separate column.

  7. Specify estimate value if you want to create ‘Estimate’ value during the import.

    1. The unit of test case ‘Estimate’ field is second. For instance, if you want to set 10 minutes as your test case estimation, you should put 600 as its value in CSV file.

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

Jira Field

Import Notes

 -

TestRay 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

  • 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

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:

  • Date Picker

  • Date Time Picker

  • 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

Custom field types:

  • Checkboxes

  • Labels

  • Select List (multiple choices)

  • You can import issues with multiple values by entering each value in a separate column.

  • Values for 'Checkboxes' and 'Select List (multiple choices)' fields require to be pre-defined in your Jira server.

  • Values for 'Labels' field are not required to be pre-defined in your Jira server, values will be created by import process.

Example:

Summary, Checkbox, Checkbox, Checkbox, Label, Label "First issue", value1, , , Label1, "Second issue", value2, , , Label1, Label2 "Third issue", value1, value2, value3, Label1,

Custom field types:

  • Number Field

  • Text Field (multi-line)

  • Text Field (single line)

  • URL Field

  • Values for those fields are not required to be pre-defined in your Jira server.

  • Values will be created by import process.

Custom field type:

  • Select List (cascading)

  • The '->' separator allows you to import the hierarchy.

  • Values for this field require to be pre-defined in your Jira server.

Example:

Summary, Cascading Custom Field Example Summary, Parent Value -> Child Value

Custom field type:

  • User Picker (single user)

  • It requires to specify Jira 'username' in csv file in order to make a successful import.

  • The user(username) specified in csv five must be defined in Jira server already.

Export Test Cases from Test Suite

There are several place to do test case export, based on which set of test cases you are planning to export.

Export Multiple Test Suites with Test Cases from a Jira Project

From ‘Tests->Test Suites’ page, click ‘Export’ button and choose test suites those you want to export.

Export a single Test Suite with its Test Cases

Launch a specific test suite and ‘Export All->Export as CSV'.

Export a sub Suite with its Test Cases

Launch a specific test suite, then find a sub suite and ‘Export->CSV’.



Â