Page History
https://cucumber.io/docs/cucumber/reporting/#built-in-reporter-plugins
Table of Contents | ||
---|---|---|
|
...
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 |
...
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution and Test fields. It allows you to send one XML file (the JUnit report) and two JSON files similar to the one Jira uses to create new issues. For more information about that second JSON format, check the Jira documentation here.
As of the creation of Test issues, some field values in the JSON file for Test Issue creation have will follow some rules:
- Issue Type: Overridden by the Test issue type;
- Summary: Overridden by the internally generated summary;
- Parent: This field is ignored;
- Project: If the there is not a Test issue with the same Generic Test Definition, then it will be created in the provided project;
- Generic Test Definition: Not allowed to provide a value for this field.
...
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution and Test Execution fields. It allows you to send one XML file (the TestNG report) and a two JSON files similar to the one Jira uses to create new issues. For more information about that second JSON format, check the Jira documentation here.
As of the creation of Test issues, some field values in the JSON file will follow some rules:
- Issue Type: Overridden by the Test issue type;
- Summary: Overridden by the internally generated summary;
- Parent: This field is ignored;
- Project: If the there is not a Test issue with the same Generic Test Definition, then it will be created in the provided project;
- Generic Test Definition: Not allowed to provide a value for this field.
Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
NUnit XML results
After executing NUnit tests, you must import the outputted XML execution results to Jira using the following endpoint:
|
NUnit XML results
After executing NUnit tests, you must import the outputted XML execution results to Jira using the following endpoint:
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||
Expand | |||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||
Responses200 OK : application/json : Successful. The results where successfully imported to Jira.
400 BAD_REQUEST : application/json : Returns the error. 401 UNAUTHORIZED : application/json : The Xray license is not valid. 500 INTERNAL SERVER ERROR : application/json : An internal error occurred when importing execution results. |
NUnit XML results Multipart
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution and Test fields. It allows you to send one XML file (the NUnit report) and two JSON files similar to the one Jira uses to create new issues. For more information about the JSON format, check the Jira documentation here.
As of the creation of Test issues, some field values in the JSON file will follow some rules:
- Issue Type: Overridden by the Test issue type;
- Summary: Overridden by the internally generated summary;
- Parent: This field is ignored;
- Project: If the there is not a Test issue with the same Generic Test Definition, then it will be created in the provided project;
- Generic Test Definition: Not allowed to provide a value for this field.
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
NUnit XML results Multipart
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.
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
|
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
Robot Framework XML results Multipart
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.
|
Robot Framework XML results Multipart
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution and Test 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.
As of the creation of Test issues, some field values in the JSON file will follow some rules:
- Issue Type: Overridden by the Test issue type;
- Summary: Overridden by the internally generated summary;
- Parent: This field is ignored;
- Project: If the there is not a Test issue with the same Generic Test Definition, then it will be created in the provided project;
- Generic Test Definition: Not allowed to provide a value for this field.
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
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 using the following endpoint:
...