Page History
...
It invokes Xray's Import Cumcumber Tests REST API endpoint (see more information here)
| field | decription |
|---|---|
| JIRA instance | The Jira instance where Xray is running. |
| Project Key | This is the project where the Tests and Pre-Conditions will be created/updated. |
| Cucumber feature files directory | This is the directory containing your feature files. All the files in this directory and sub directories will be imported. |
| Modified in the last hours | By entering an integer n here, only files that where modified in the last n hours will be imported. Leave empty if you do not want to use this parameter. |
...
| format and specific endpoint | field | description | |||||
|---|---|---|---|---|---|---|---|
Behave JSON multipart Cucumber JSON multipart NUnit XML multipart JUnit XML multipart Robot XML multipart TestNG XML multipart | Test execution fields | An object (JSON) specifying the fields for the issue. You may specify the object either directly in the field or in the file path.
| |||||
NUnit XML JUnit XML Robot XML TestNG XML | Import to Same Test Execution | When this option is check, if you are importing multiple execution report files using a glob expression, the results will be imported to the same Test Execution | |||||
| Project key | Key of the project where the Test Execution (if the Test Execution Key field wasn't provided) and the Tests (if they aren't created yet) are going to be created | ||||||
| Test execution key | Key of the Test Execution | ||||||
| Test plan key | Key of the Test Plan | ||||||
| Test environments | List of Test Environments separated by ";" | ||||||
| Revision | Source code's revision being target by the Test Execution | ||||||
| Fix version | The Fix Version associated with the test execution (it supports only one value) |
...