Page History
...
For each import file format, Xray provides a specific REST endpoint:
Xray JSON format | /api/v1/import/execution |
Xray JSON format Multipart | /api/v1/import/execution/multipart |
Cucumber JSON output format | /api/v1/import/execution/cucumber |
Cucumber JSON output format Multipart | /api/v1/import/execution/cucumber/multipart |
JUnit XML output format | /api/v1/import/execution/junit |
JUnit XML output format Multipart | /api/v1/import/execution/junit/multipart |
NUnit XML output format | /api/v1/import/execution/nunit |
NUnit XML output format Multipart | /api/v1/import/execution/nunit/multipart |
xUnit XML output format | /api/v1/import/execution/xunit |
xUnit XML output format Multipart | /api/v1/import/execution/xunit/multipart |
TestNG XML output format | /api/v1/import/execution/testng |
TestNG XML output format Multipart | /api/v1/import/execution/testng/multipart |
Robot Framework XML output format | /api/v1/import/execution/robot |
Robot Framework XML output format multipart | /api/v1/import/execution/robot/multipart |
Xray JSON results
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. Alternatively, you can create a new Test Execution for the execution results and specify the Test Execution issue fields in the info object.
...
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
|
...
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
...
Xray provides another endpoint if you want to create new Test Executions and have control over the fields of newly - created Test Execution fields. It allows you to send one Executions and Tests. The endpoint accepts one XML file (the JUnit report) and a two JSON files similar to the one Jira uses to create new issues, one with the fields of the Test Execution and the other with the fields of the Test. For more information about that second JSON format, check the Jira documentation here. Xray will ignore the issue type and the summary fields on the Test JSON file since these are provided by the importation.
Expand | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
|
...
Xray provides another endpoint if you want to create new Test Executions and have control over the fields of newly - created Test Execution fields. It allows you to send one Executions and Tests. The endpoint accepts one XML file (the TestNG NUnit report) and a two JSON files similar to the one Jira uses to create new issues, one with the fields of the Test Execution and the other with the fields of the Test. For more information about that second JSON format, check the Jira documentation hereJira documentation here. Xray will ignore the issue type and the summary fields on the Test JSON file since these are provided by the importation.
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
|
...
Xray provides another endpoint if you want to create new Test Executions and have control over the fields of newly - created Test Execution fields. It allows you to send one Executions and Tests. The endpoint accepts one XML file (the xUnit report) and a two JSON files similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here, one with the fields of the Test Execution and the other with the fields of the Test. For more information about that JSON format, check the Jira documentation here. Xray will ignore the issue type and the summary fields on the Test JSON file since these are provided by the importation.
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
|
...
Expand | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||
|
...
Xray provides another endpoint if you want to create new Test Executions and have control over the fields of newly - created Test Execution fields. It allows you to send one Executions and Tests. The endpoint accepts one XML file (the NUnit TestNG report) and a two JSON files similar to the one Jira uses to create new issues, one with the fields of the Test Execution and the other with the fields of the Test. For more information about that second JSON format, check the Jira documentation hereJira documentation here. Xray will ignore the issue type and the summary fields on the Test JSON file since these are provided by the importation.
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
|
Robot Framework XML results
After executing Robot Framework tests, you must import the outputted XML execution results to Jira using the following endpoint:
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
Robot Framework XML results Multipart
Xray provides another endpoint if you want to have control over the fields of newly created Test Executions and Tests. The endpoint accepts one XML file (the Robot report) and two JSON files similar to the one Jira uses to create new issues, one with the fields of the Test Execution and the other with the fields of the Test. For more information about that JSON format, check the Jira documentation here. Xray will ignore the issue type and the summary fields on the Test JSON file since these are provided by the importation.
Expand | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|