Page History
...
| Info | ||
|---|---|---|
| ||
This procedure allows you to migrate the essential of Test's specification. If you need to migrate run's and other information then this procedure is non-applicable; the REST API may be used but it will require some work from your side since there is no direct way to migrate it. |
Importing executions related information from a legacy (non-JIRA) test management tool to Xray on JIRA
Although Xray allows you to import execution related information, currently Xray does not provide an out-of-the-box solution for migration execution related information along with respective tests from other systems.
| Info | ||
|---|---|---|
| ||
| This approach requires some development effort from your side. |
- Migrate Tests specification
- From CSV using Test Case Importer; supports attachment => you will miss the mapping information between original_idócreated_issue_key; you wil have to somehow manage it
- Programmatically create the Test issues using JIRA’s REST API (some examples in http://confluence.xpand-addons.com/display/XRAY/Tests+-+REST#Tests-REST-CreatingandEditingTests-JIRARESTAPI ); this will allow you to easily identify the mapping original_idócreated_issue_key , which can be used afterwards
2. Migrate organization (optional; not really necessary)
=> This depends greatly on the legacy system organization. If it groups somehow tests, then the JIRA REST API can be used to create the Test Set issues. After that, Xray’s REST API can be used in order to add the Tests. It is required to know the Tests issue keys in advance.
3. Import results
a) Create Test Executions with the respective Tests
=> For this, JIRA REST API can be used to create the Test Execution issue. After that, Xray’s REST API (i.e. POST /rest/raven/1.0/api/testexec/{testExecKey}/test) can be used in order to add the Tests. It is required to know in advance the Tests issue keys.
b) Import results for each Test Execution
- Import just overall test result, for each test run that is part of the test execution
- Import detailed test run results, including per step information
=> Each approach can be achieved using the REST API, and the POST /rest/raven/1.0/import/execution endpoint. You just need to know in advance the Test Execution key and also the issues keys for each Test that is part of the Test Execution.