14 January 2019
The Xray team is proud to announce the release of Xray 3.3.0.
The main feature of this version is the ability to easily migrate Xray related information from one JIRA instance to another; you may use Jira's backup&restore facilities to fully restore a project, including testing related data. Besides this, we also include a built-in Zephyr migration utility, so you can start taking advantage of Xray right-away.
Users using Structure will love the new enhancements available in the Xray extender, which now will also include the ability to manage the relation between Test Plans and Test Executions.
We know that the Traceability Report is important and quite useful to you; thus we added quick coverage status based filtering and also the ability to see all requirements at same level, as we had on earlier releases.
As part of our continuous improvement, more performance improvements landed in this version, for the most intensive gadgets/reports and JQL functions.
Discover the key features below
Upgrading to Xray 3.3.0
After installing version 3.3.0 of Xray, if you upgrade 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 upgrade. A re-index operation of your Jira instance is required so that the internal data becomes searchable and usable by Xray.
If you upgrade from v3.2.x to v3.3.y, you must recalculate data in Xray configuration section → Custom Fields. This recalculation is necessary because of a huge improvement in the amount of data that Xray need to add to the table and to Lucene indexes.
Downgrading from Xray 3.3.x
Downgrading from Xray 3.3.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.
Move data/restore projects between Jira instances
For restoring projects, Jira offers the built-in "Project Import" tool which allows partial, project imports (i.e. importing a specific project from a previous backup).
This tool has some limitations though; it cannot transfer apps/add-ons related data between instances unless apps are prepared for it.
Fortunately, since v3.3, Xray is able of taking advantage of this mechanism; on previous versions, issues would be restored but the testing data wouldn't.
Thus, you can now use built-in backup&restore facilities of Jira:
- for copying a project from one Jira instance to another Jira instance (e.g. from staging to production, or from internal to a DMZ instance)
- to restore a project upon some mistake/data loss has been done in that project within an existing Jira instance
Learn more here.
Built-in Zephyr for Jira migration utility
Xray now provides a built-in migration utility for Zephyr for Jira, so you can easily migrate to Xray and take advantage of the many features Xray provides over Zephyr.
As you may still have some projects using Zephyr for Jira, you may now inline migrate the Tests and related data to Xray following a wizard.
This specific utility is available in Jira administration, under System > Import and Export > External System Export.
Learn more here.
Enhanced existing gadgets with time based filtering and more
Besides adding time based filters to the Test Runs Summary gadget, now you can also group Test Runs by Test (key).
The Test Evolution, Test Runs List, Test Runs Summary gadgets were all improved so that you may see results for the last X number of days.
This will allow you to see and assess only the most recent information based on the information of the past days.
Learn more about these and all other gadgets here.
Enhanced Structure Extender
If you're using Structure app to view and manage Xray related entities right from a "structure", the enhanced Xray extender now provides the ability to:
- see and manage associations between Test Plans and Test Executions
- choose to synchronize Tests to Test Plans whenever adding/removing Tests from the related Test Executions (e.g. if you add a Test to Test Execution, it can automatically be added to the related Test Plan(s))
- choose whether to manage or not Tests directly under Test Plans
Learn more here.
Flat presentation and coverage filters on the Traceability Report
The Traceability Report was enhanced in order to support hierarchical and flat presentation.
Whenever using the hierarchical presentation (which was previously the default) the "requirements" and the child/sub-requirements are shown; in this case the Filter is used to select the parent requirements. Whenever using "flat" presentation, all "requirements" are shown at the same level; in this case, the Filter applies to all of them.
It is also now possible to apply some quick filters, in this case on the coverage. Thus, you can filter out only uncovered requirements or only the requirements that are NOK, for example; or a mix of coverage status if you want. By providing counters for each coverage status, you can quickly evaluate the amount of requirements that are currently in a certain status and that may need some attention.
Learn more here.
As part of our continuous performance improvements, we've improved several areas from reports/gadgets to functions.
The most intensive task related with calculation of coverage is now pre-calculated, which should provide quite noticeable performance improvements.
In sum, we've improved performance on:
- Test Lists gadget;
- Overall Requirement Coverage gadget & report;
- Historical Requirement Coverage gadget & report;
- requirements() and requirementsWithStatusByTestPlan() JQL functions.
Improving performance is an ongoing effort, so expect additional enhancements to come ahead.
- Support for Test Execution filter as argument in the testPlanTestExecutions() JQL function
- Return ids of step and attachments whenever updating or creating Test steps
- Enhanced integration with Xporter, in terms of performance and also by providing access to the Test Run rank within a Test Execution
New Features and Bug Fixes in this release