7 November 2016

The Xray for JIRA team announces the release of Xray 2.0.0. Version 2.0 is a step forward in Test Management!

We listened to your feedback and we have improved many aspects of Xray. And more is coming in the future.

This new major version brings also new concepts and many enhancements besides the usual bug fixes.

Upgrading to Xray 2.0.0

Re-indexing JIRA

After installing version 2.0.0 of Xray for JIRA, a re-index operation of your JIRA instance is required. This is because some Xray custom fields need to be indexed in order to be searchable.

New Xray issue type icons

Version 2.0.0 of Xray brings new icons to it's issue types. You may need to restart JIRA in order for the icons to be applied.

Breaking Changes

The "Requirement Status" custom field may no longer be available on existing Agile boards, and gadgets. This was due to a change in the custom field type. You'll need to configure the board cards and gadgets to the custom field again

Highlights for this release

Test Plans

Until now you had to organize your tests in Test Sets. And that makes all sense.

But one thing is organizing the tests, by grouping them, and another thing is planning tests for a given release.

With Xray 2.0 we've introduced the Test Plan, so you can create and manage your tests effectively. Assign one, or more, Test Plans to a given release and track progress of the tests within each Test Plan.

You can even see the requirement coverage taking into account the Test Plan tests.

You can now easily create Test Executions for the failing tests, or other, from within a Test Plan.

Executions for multiple Test Environments

The Test status was calculated by looking at the test's last execution. But this does not work well if you execute the same test in two different devices and you want the status to be like a "merge" of the two results.

Within a Test Execution you can now specify the Test Environment(s) where the tests will be executed. A Test Environment is similar to a label, but Xray provides some special logic to deal with it. Let's say that you have executions for three Test Environments: "Chrome", "Safari" and "Firefox". The test is considered as PASS only if the latest executions for Chrome, Safari and Firefox are all PASS; it will be FAIL if any of them has failed.

Learn more here.

Multiple Pre-Conditions

Xray supports, since day one, Pre-Conditions as a way to define initial conditions that should be met before executing a Test. This is very useful whenever you have to start by doing exactly the same thing in your tests. But sometimes you have to do several things  (e.g. restore DB, authenticate) before your Test steps.

Each of those things may be used independently (e.g. some Test may require just to restore the DB, another may require just to authenticate, and others may require that both things, or even more, need to be done before starting executing the steps).  Now you can assign multiple Pre-Conditions to a given Test. 

Redesigned execution page

The execution page had a major facelift!

Our aim was to improve the overall user experience.

Since testers spend most of their time executing tests, we analyzed the process and made it more obvious and pleasant to work with.

You may notice that the "inputs" and the "output/results" of the test are now horizontally grouped. Besides that, the step status now reflects itself on the color of the step.

Agile Enhancements

From within the Agile board or in the backlog you can see the requirement status, so you're always in control. 

In the Agile board, you can also see requirement's related executions, using Sub Test Executions. 

Learn more  here.


A Sub Test Execution has exactly the same functionalities as the Test Execution issue type. The difference between them is that the Sub Test Execution is a sub-task and can be created in a requirement's context.

Besides the direct visibility on the Agile board, creating a Test Execution as a sub-task of the requirement issue will provide the user the ability to better track time estimates.

Learn more here.

Custom Manual Test Step Statuses

Although we already supported  custom test statuses, Xray now adds the ability of defining custom step statuses and their mapping to the Test status, giving you more configuration flexibility.

Learn more here.

Improved REST API

We have improved the traceability in the REST API in order to make it easier to correlate and navigate between entities.

As an example you can now easily obtain the Test Sets or Test Executions related with a given Test... or you can obtain the Test and Test Execution related with a given Test Run.

Of course, we've added specific endpoints for Test Plans.

And, in between, we have updated the whole REST API with more examples.

Learn more here.

Revamped Documentation

The documentation was completely reviewed, reorganized and is now more extensive and detailed in many areas. We have added many diagrams to make things clearer.

Some pages worth giving a look include the whole Testing with Xray, Project Organization Use Cases, Test Process, Terms and Concepts, Examples of Reports Built with Xporter, Examples of custom gadgets, FAQ, just to name a few.

We invite you to explore Xray's complete documentation starting with the Xray Documentation Home page.

And much more...

UX & UIAdministrationOther
  • Ability to associate tests to existing Pre-Condition(s) in the Test creation dialog 

  • Create Tests, and Sub Test Executions, directly from the requirement issue screen

  • Execute tests in and change status in bulk for multiple tests 

  • New Test Coverage section in the requirement issue screen, with list of tests and their status 

  • Filter by requirement's Resolution in requirement coverage panel 

  • Ability to configure columns both in the Test Runs panel inside the Test issue screen and also in the Tests panel inside the Test Set issue screen

  • Completely revamped execution screen, more consistent, clearer and user friendly
  • Ability to transition Test Execution status accordingly with the results of its tests  

  • Ignore requirements in coverage charts based on requirement's specific label(s)

  • Ability to define a project as a "requirements project"
  • CSV export improvements (e.g. list of tests related with test executions, list of pre-conditions related with tests)

  • JQL functions to support Test Plan and more

  • Translations for French and Spanish

New Features and Bug Fixes in this release


Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  • No labels