Page History
...
Xray JSON format | /rest/raven/1.0/import/execution |
Xray JSON format multipart | /rest/raven/1.0/import/execution/multipart |
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 |
TestNG XML output format | /rest/raven/1.0/import/execution/testng |
TestNG XML output format multipart | /rest/raven/1.0/import/execution/testng/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 |
xUnit XML output format | /rest/raven/1.0/import/execution/xunit |
xUnit XML output format multipart | /rest/raven/1.0/import/execution/xunit/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 |
"summary"
:
"Update existing test"
,
compressed zip file to import or a JSON file to import.
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.
Updating an existing Test Run using Xray format REST API will reset all dataset related fields. This means that all current iteration data and dataset present in the Test Run will be replaced with the new information given in the REST API request.
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
|
...
Xray provides another endpoint if you want to create or update a Test Executions and have control over all Test Execution fields. It allows you to send two JSON files, the normal Xray JSON result and a JSON similar to the one Jira uses to create/update issues. For more information about that second format, check the Jira documentation here. Note that in this endpoint the info
property in the Xray Json result part will be ignored.
Updating an existing Test Run using Xray format REST API will reset all dataset related fields. This means that all current iteration data and dataset present in the Test Run will be replaced with the new information given in the REST API request.
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
...