19 September 2019
The Xray team is proud to announce the release of Xray 3.5.0.
The main goal for this version is to improve filtering capabilities on Test Executions and also Test Coverage reports such as the Overall Coverage and the Traceability report. Users can now choose any field in Jira to filter and also use JQL.
Another relevant feature is the ability to provide a custom JSON file when importing execution results to specify how the Tests will be created in Jira.
As part of our continuous improvement, more performance improvements have also been included in this version.
Discover the key features below.
Upgrading Xray to 3.5.x
Upgrading from versions < 3.2.0
If you are upgrading from a version lower than 3.2, this implies that an upgrade task will run to pre-calculate historical data. This action is a one time action and it will run in the background so that Xray is still available during the upgrade. A re-index operation of your Jira instance is required so that the internal data becomes searchable and usable by Xray.
Upgrading from versions >= 3.2.x
If you are upgrading from v3.2.x or v3.3.x to v3.4.y, you must recalculate data in the Xray configuration section → Custom Fields. This recalculation is necessary because of the huge improvement in the amount of data that Xray needs to add to the table and to Lucene indexes.
Downgrading from Xray 3.5.x
Downgrading from Xray 3.4.x to a version less than 3.2.0 implies that you must perform a re-index afterwards. This is because from Xray 3.2.0 onwards, the content and format of what Xray indexes has changed.
Historical Coverage Gadget
Some configuration parameters for this gadget where modified as a result of supporting multiple projects whenever using a saved filter as source. It is possible that some users will get errors on the gadget after downgrading from 3.4.x. If this happens, please edit the configuration to ensure the gadget is properly configured.
Release highlights
Filters with customizable fields and JQL
Xray v3.4 adds a set of features that enable the basics of Risk-Based Testing (RBT); more about these enabling features ahead.
As always, we made it flexible enough so you can implement RBT the way you want. Thus, you may need to set up some custom fields related to RBT. For this, you may use Jira built-in capabilities or use a customization app to help you. If you're using a "compatible" Risk Management related app, you may also take advantage of it.
To make it simpler, we've included detailed setup instructions in our documentation.
Learn more here.
Importing execution results with a JSON template for creating Test cases
It is now possible to import execution results and provide a JSON template document to create Test cases. Possible usage scenarios include required fields in Test issues and any additional information for Test cases when they are created automatically by Xray.
Learn more about importing execution results here.
Performance improvements
As part of our continuous performance improvements, we have improved performance on the Requirement issue's Test Coverage web panel.
Improving performance is an ongoing effort, so expect additional enhancements to come ahead.
Please take a look at Usage tips to improve performance, containing setup and usage best practices.
And more...
Gadgets | Test Repository | Execution |
---|---|---|
|
|
|
New Features and Bug Fixes in this release