Page History
...
- Configuration alias: a friendly name for the configuration
- Server or Cloud: Cloud
- Authentication:
Build Steps
Build steps are the building blocks of the build process. These need to be defined in the build configuration.
...
- one build step for exporting Cucumber Scenario/Scenario Outlines from Jira as .feature files
- one build step for importing Cucumber Tests from existing Cucumber features into Jira.
- one build step which that publishes the execution results back to Jira.
...
This build step will export the Cucumber Tests (i.e., Scenario/Scenario Outlines) in .feature or bundled in a .zip file. The rules for exporting are defined here.
It invokes Xray's Export Cucumber Tests REST API endpoint (see more information: server or cloud).
Configuration
Some fields need to be configured in order to export the Cucumber Tests. As input, you can either specify issue keys (see the endpoint documentation for the server or documentation for the server or cloud) or the ID of the saved filter in Jira.
...
This build step is only available for the server and 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.
It invokes Xray's Import Cumcumber Cucumber Tests REST API endpoint (see more information here).
| Field | Description | 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 here, only files that where were modified in the last n hours will be imported. Leave empty if you do not want to use this parameter. |
...
The app provides easy access to Xray's Import Execution Results REST API endpoints (see more information for theserver or cloud). Therefore, it mimics the endpoints endpoint's input parameters.
It supports importing results in Xray's own JSON format, Cucumber, Behave, JUnit, and NUnit, among others. However, there are some endpoints in the server that may not yet be available for Xray Cloud.
...
| 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) |
Examples
Cucumber
In a typical Cucumber typical Cucumber Workflow, after having created a Cucumber project and the Cucumber tests specified in Jira, you may want to have a project that exports the features from Jira, executes the automated tests on a CI environment and environment, and then imports back its results.
...