Page History
Table of Contents | ||
---|---|---|
|
Importing Execution Results
Execution results can be imported to JIRA Jira through JSON/XML representation formats specified in Import Execution Results.
For each import file format, Xray provides a specific REST endpoint:
Xray JSON format | /rest/raven/1.0/import/execution |
Cucumber JSON output format | /rest/raven/1.0/import/execution/cucumber |
Cucumber JSON output format multipart | /rest/raven/1.0/import/execution/cucumber/multipart |
Behave JSON output format | /rest/raven/1.0/import/execution/behave |
Behave JSON output format multipart | /rest/raven/1.0/import/execution/behave/multipart |
JUnit XML output format | /rest/raven/1.0/import/execution/junit |
Junit XML output format multipart | /rest/raven/1.0/import/execution/junit/multipart |
NUnit XML output format | /rest/raven/1.0/import/execution/nunit |
NUnit XML output format multipart | /rest/raven/1.0/import/execution/nunit/multipart |
Robot Framework XML output format | /rest/raven/1.0/import/execution/robot |
Robot Framework XML output format multipart | /rest/raven/1.0/import/execution/robot/multipart |
Compressed .zip file (e.g., Calabash execution results) | /rest/raven/1.0/import/execution/bundle |
...
When importing execution results using Xray JSON result format in a Continuous Integration environment, you can specify which Test Execution issue to import the results on using the "testExecutionKey" property or . Alternatively, you can create a new Test Execution for the execution results specifying and specify the Test Execution issue fields in the "info" object.
...
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
After executing Cucumber features, you must import the outputted JSON execution results to JIRA Jira using the following endpoint:
...
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Cucumber JSON results Multipart
Besides the above mentioned endpoint Xray provides another one for users that endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. The way Xray provides this is by allowing the user to sent two json It allows you to send two JSON files, the normal cucumber Cucumber result json JSON and a json JSON similar to the one JIRA one Jira uses to create new issues for . For more information about that json format check JIRA second format, check the Jira documentation here.
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
|
...
After executing Behave features, you must import the outputted JSON execution results to JIRA Jira using the following endpoint:
...
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Behave JSON results Multipart
Besides the above mentioned endpoint Xray provides another one for users that endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. The way Xray provides this is by allowing the user to sent two json It allows you to send two JSON files, the normal behaveBehave's result json JSON and a json JSON similar to the one JIRA one Jira uses to create new issues for . For more information about that json format check JIRA second format, check the Jira documentation here.
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
After executing JUnit tests, you must import the outputted XML execution results to JIRA Jira using the following endpoint:
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
JUnit XML results Multipart
Besides the above mentioned endpoint Xray provides another one for users that endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. The way Xray provides this is by allowing the user to sent one It allows you to send one XML file (the JUnit report) and a json file JSON similar to the one JIRA one Jira uses to create new issues. For more information about that json format check JIRA second format, check the Jira documentation here.
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
After executing NUnit tests, you must import the outputted XML execution results to JIRA Jira using the following endpoint:
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
NUnit XML results Multipart
Besides the above mentioned endpoint Xray provides another one for users that endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. The way Xray provides this is by allowing the user to sent one It allows you to send one XML file (the NUnit report) and a json file JSON similar to the one JIRA one Jira uses to create new issues. For more information about that json format check JIRA documentation second format, check the Jira documentation here.
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
Robot Framework XML results
After executing Robot Framework tests, you must import the output XML execution results to JIRA Jira using the following endpoint:
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
Robot Framework XML results Multipart
Besides the above mentioned endpoint Xray provides another one for users that endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. The way Xray provides this is by allowing the user to sent one It allows you to send one XML file (the Robot report) and a json file JSON similar to the one JIRA one Jira uses to create new issues. For more information about that json format check JIRA second format, check the Jira documentation here.
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
In order to import multiple execution results (e.g., outputted from Calabash or Xamarin Test Cloud), you must import the bundled compressed file with multiple execution results to JIRA Jira using the following endpoint:
...
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
...