2 October 2015

The Xray for JIRA team announces the release of Xray 1.10.0. This point release contains several new features and bug fixes.

Highlights for this release

Set affected Requirement Statuses

Xray for JIRA now provides the ability to manually set the status for requirements in the context of a particular execution. It might be the case that you have a Test that covers multiple requirement issues and those requirements definitions do not have anything in common. In this case, if the Test fails, this does necessarily not mean that all requirements affected by this Test are NOK also. Therefor, in the execution screen, you can know see a new section with the affected requirement issues and you can set the status for each of them. These execution context requirement statuses will then be considered in the requirement status calculation.


Map Custom Test Statuses to Requirement Statuses


Custom test statuses can now be mapped to specific requirement statuses. Therefor when you create a new custom status for Tests, you can now map it to one of the available requirement status. Also, a new requirement status called UNKNOWN is available. This is the default requirement status that is mapped to custom test statuses.

Disallow executions on Test Executions with a specific workflow status


Starting from Xray version 1.10.0 you will be able to configure which JIRA workflow statuses will disallow the execution of Test Runs. For instance, if you configure the "Closed" status, then Test Execution issues that are "Closed" will not allow Test Run executions.



New Features and Bug Fixes in this release


T Key Summary P Status Resolution

  • No labels