Execution results can be imported to 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 |
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 |
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. Alternatively, you can create a new Test Execution for the execution results and specify the Test Execution issue fields in the "info" object.
|
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.
|
After executing Cucumber features, you must import the outputted JSON execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send two JSON files, the normal Cucumber result JSON and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
After executing Behave features, you must import the outputted JSON execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send two JSON files, the normal Behave's result JSON and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
After executing JUnit tests, you must import the outputted XML execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send one XML file (the JUnit report) and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
After executing TestNG tests, you must import the outputted XML execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send one XML file (the TestNG report) and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
After executing NUnit tests, you must import the outputted XML execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send one XML file (the NUnit report) and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
After executing Robot Framework tests, you must import the output XML execution results to Jira using the following endpoint:
|
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution fields. It allows you to send one XML file (the Robot report) and a JSON similar to the one Jira uses to create new issues. For more information about that second format, check the Jira documentation here.
|
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 using the following endpoint:
|
Whenever importing results from some frameworks (i.e. JUnit, TestNG, NUnit, Robot framework), Xray can identify the automated test from the report/results file, based on an hardcoded criteria (such as the class name plus the class method corresponding to the automated test). However, depending on the test automation framework, it's possible to specify the Test issue key to which report the results in the test's code.
Independently of whether the test is identified implicitly (based on some attributes present in the test result file) or explicitly (based on the provided Test key), related Test Runs are always reported against the correct Test issue. As a consequence, if you report results multiple times there won't be duplicated Test entities.
When the identification is implicit, Xray is able to create (Generic) Test entities, if needed, per each automated test; these will be reused afterwards in similar cases.
Whenever processing results from a automation framework, for each automated test result,
For some frameworks, including Cucumber and Behave, Tests must exist previously to the submission of results related to them.
The reason for it,resides mainly in the fact that is not possible to create the complete Test specification from the results file.