Overview

Xray enables easy integration with Bamboo through the "Xray for JIRA add-on for Bamboo", providing the means for successful Continuous Integration by allowing users to report automated testing results.

Release Notes

• Xray Connector for Bamboo 1.2.2 Release Notes
• Xray Connector for Bamboo 1.2.1 Release Notes
• Xray Connector for Bamboo 1.2.0 Release Notes
• Xray Connector for Bamboo 1.1.3 Release Notes
• Xray Connector for Bamboo 1.1.2 Release Notes
• Xray for JIRA add-on for Bamboo 1.1.1 Release Notes
• Xray for JIRA add-on for Bamboo 1.1.0 Release Notes
• Xray for JIRA add-on for Bamboo 1.0.1 Release Notes
• Xray for JIRA add-on for Bamboo 1.0.0 Release Notes

Installation

The installation can be made either automatically or manually. 

Automatic Installation

You can install Xray for Bamboo through the Universal Plugin Manager (UPM). Go to Bamboo's administration, then select Add-ons > Find new add-ons. 

Manual Installation

If you have the actual xray-bamboo-X.X.X.jar file, 

1. Go to the administration section of Bamboo, look for the Add-Ons > Manage Add-Ons menu.
2. Select option Upload Add-On and upload the xray-bamboo-X.X.X.jar file, where X.X.X is the file version.

Configuration

Xray for Bamboo is configured in Bamboo Administration page, in the  Add-Ons > Xray for JIRA configuration.

Jira servers

The Jira servers configuration defines connections with Jira instances. 

To add a new Jira instance connection, specify these properties:

1. Name: Configuration alias
2. Server Address: the address of the JIRA Server where Xray is running
3. Authentication information:
   
   1. User: username
   2. 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.

Xray: Cucumber Features Export Task

This task 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 here).

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 documention here) or the ID of the saved filter in Jira.

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.

It supports importing results in Xray's own JSON format, Cucumber, Behave, JUnit, and NUnit, among others.

Configuration 

Additional fields

Depending on the chosen test result format, some additional fields may need to be configured.

Examples

Cucumber

In a typical Cucumber Workflow, after having created a Cucumber project and the Cucumber tests specified in Jira, you may want to have a plan that exports the features from Jira, executes the automated tests on a CI environment, and then imports back its results.

For this scenario, the Bamboo plan would be configured with a set of tasks responsible for:

1. Pulling the Cucumber project
2. Exporting Cucumber features from Jira to your Cucumber project
3. Executing the tests in the CI environment
4. Importing the execution results back to Jira

Exporting Cucumber features

To start the configuration, add the task Xray: Cucumber Features Export Task. After that, configure it and click Save.

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

To start the configuration, add the task Xray: Results Import Task. After that, configure it and click Save.

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:

• Insert the relative path to the JSON file containing the information, or
• Insert the JSON content directly in the field.
  
  

In this example, we configured the following object:

{
   "fields": {
      "project": {
         "key": "PROJ"
      },
      "summary": "Test Execution for Cucumber results (Generated by job: ${bamboo.buildKey})",
      "issuetype": {
         "id": "10102"
      }
   }
}

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.

If you want to import JUnit XML reports, a typical Job outline would be:

1. Pulling the JUnit project
2. Executing the tests in the CI environment
3. Importing the execution results, including Tests, to Jira.

Importing the execution results

To start the configuration, add the task Xray: Results Import Task. After that, configure it and click Save.

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

The build process is failing with status code 403

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.