Page History
| Table of Contents |
|---|
...
- Name: Configuration alias
- Server Address: the address of the JIRA Server where Xray is running
- Authentication information:
- User: username
- Password.
Tasks
The app provides a task for exporting Cucumber Scenario/Scenario Outlines from Jira as .feature files, and another task for importing execution results.
...
In this example, we configured the task to extract the features from a set of issues (PROJ-78 and PROJ-79) to the folder that holds the Cucumber project.
Importing the execution results
...
In this example, we configured the task to import the Cucumber JSON results back to Jira.
After running the plan, the expected result is a new Test Execution issue created in the Jira instance.
Importing the execution results with user-defined field values
For Cucumber, Behave, JUnit, NUnit and Robot, Xray for Bamboo allows you to create new Test Executions and have control over newly-created Test Execution fields. You can send two files, the normal execution result file and a JSON file similar to the one Jira uses to create new issues. More details on how Jira creates new issues can be found here.
For this scenario and example, the import task needs to be configured with Cucumber JSON Multipart format. When selecting this option, you can, additionally, configure the Test Execution fields in two ways:
...
And configured the task to import the Cucumber JSON Multipart results back to Jira.
After running the plan, the expected result is a new Test Execution issue created in the Jira instance, with the Test Execution fields as specified in the Bamboo task configuration.
JUnit
Apart from supporting Cucumber natively, Xray enables you to take advantage of many other testing frameworks like JUnit. In this sense, Xray for Bamboo lets you import other results in other formats besides Cucumber JSON.
...
In this example, we have a configuration where the JUnit XML format is chosen.
After running the plan, the expected result is a new Test Execution issue created in the Jira instance.
Troubleshooting
...
When you check its log, it has the following:
By default, when you have successively tried to log into Jira with the wrong credentials, the Jira instance will prompt you to provide a CAPTCHA the next time you try to do so. It is not possible to provide this information via the build process, so it will fail with status code 403 Forbidden.
You will need to log in to Jira via the browser and provide the CAPTCHA.
If you are a Jira administrator, you can go to Jira administration > User Management and reset the failed login.
