Xray Exporter is a tool used to export test cases into Jira Xray Plugin.
Features:
|
Note
|
The properties marked with bold are mandatory. |
| Property | Required | Description |
|---|---|---|
|
false |
The key of the configured JIRA instance, in case of missing value it will be evaluated automatically based on issue keys being exported |
|
true |
Path to directory with test execution JSON results. The path is managed by the Please make sure that the |
|
true |
Key of a Jira project where new test cases should be created |
|
false |
Username of Jira user that will be used as assignee for newly created test cases |
|
false |
Statuses of test cases allowed to update |
|
false |
The key of a |
|
false |
By default, the content of Test Cases that have associated IDs, is updated every export run, to disable this behavior set the value of this property to |
|
false |
Comma-separated list of file and folder paths that should be uploaded to test execution as attachments. Please note that regular files like images, texts are uploaded as is, whereas folders are archived before the upload. |
xray-exporter.project-key=ABBA
xray-exporter.json-results-directory=/Users/happytester/Repositories/app-tests/output/results/jbehave| Property | Required | Description |
|---|---|---|
|
false |
The key of |
|
false |
The |
Test execution import varies depending on values in xray-exporter.test-execution-key and xray-exporter.test-execution-summary, the following matrix shows this behavior change:
| Configuration | Result |
|---|---|
Both |
Test execution summary and associated test cases will be updated, the update of test cases is performed according to following rules:
|
Only |
New test execution will be created |
Only |
Associated test cases will be updated according to following rules:
|
Neither |
Text execution import is skipped |
The Xray is a Jira plugin that uses custom Jira fields for it’s data, one of the ways to find out custom field names for particular field used by Xray on Jira UI (if access to Jira configuration is prohibited) is to request description of some issue like https://jira.example.com/rest/api/latest/issue/DUMMY-1.
| Index | Property | Description |
|---|---|---|
|
Key of a field containing test case type |
|
|
Key of a field containing collection of manual steps |
jira.<jira instance key placeholder>.fields-mapping.test-case-type=customfield_10001
jira.<jira instance key placeholder>.fields-mapping.manual-steps=customfield_10002
| Index | Property | Description |
|---|---|---|
|
Key of a field containing test case type |
|
|
Key of a field containing type of cucumber scenario |
|
|
Key of a field containing body of cucumber scenario |
jira.<jira instance key placeholder>.fields-mapping.test-case-type=customfield_10003
jira.<jira instance key placeholder>.fields-mapping.cucumber-scenario-type=customfield_10004
jira.<jira instance key placeholder>.fields-mapping.cucumber-scenario=customfield_10005| Name | Example | Description |
|---|---|---|
|
|
Map scenario to Jira test case in 1 to 1 relation |
|
|
Link scenario to Jira issue with "Tests" link type in 1 to 1 relation |
|
|
Set labels to the exported test case |
|
|
Set components to the exported test case |
|
|
Skip test case while exporting |