Page History
...
| field | description |
|---|---|
| Jira instance | The Jira instance where Xray is running |
| Issue keys | Set of issue keys separated by ";" |
Filter ID | A number that indicates the filter ID |
| File path | The relative path of the directory where the features should be exported to; normally, this corresponds to the "features" folder of the Cucumber project that has the implementation steps. Note: The directory will be created if it does not exist. |
Xray: Cucumber Features Import Task
This build step will import existing cucumber Tests from existing Cucumber feature files into Xray issues. This Task will import from .feature files and also from .zip files.
This task 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. |
Xray: Results Import Task
The app provides easy access to Xray's Import Execution Results REST API endpoints (see more information here). Therefore, it mimics the endpoints input parameters.
...