xx December 201814 January 2019

The Xray team is proud to announce the release of Xray 3.3.0.

...

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.

...

After installing version 3.3.0 of Xray, if you upgrade from a version less lower than 3.2, a , 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. Otherwise, if

If you upgrade from v3.2.x to v3.3.y, no re-index should be neededyou 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

...

Panel
borderColor #F3F3F3 bgColor #FAFAFA borderWidth 1px
Section Flat presentation and coverage filters on the Traceability Report Column width 50% 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. Column width 50% Image Added

Email Notifications for changes on the specifications of Tests and Pre-Conditions

Panel
borderColor #F3F3F3 bgColor #FAFAFA borderWidth 1px
Section Performance improvements Column width 50% Image Added Image Removed Column width 50% 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. Column width 50%
Panel
borderColor #F3F3F3 bgColor #FAFAFA borderWidth 1px
Section

We know that the editing of Tests is quite dynamic. Some users want to get notified upon every change in the Test/Pre-Condition specification, while others don't.

Since Test cases are abstracted as Jira issues, you can also have changes on all the standard fields at the issue level.

On the other hand, Jira's notification schemes don't allow you to define notifications on a per-issue-type basis, and you may want to get updates on Stories and Bugs but not on Tests, or vice-versa.

Thus, we have created a specific event that will be triggered whenever the specification of a Test/Pre-Condition is changed, giving you the ability to define notifications for it.

It will be triggered upon:

• adding/removing/updating steps in Manual Tests
• updating the "Generic Test Definition" of Generic Tests
• updating the "Cucumber Scenario" of Cucumber Tests
• updating the "Conditions" of Pre-Conditions.

Learn more here.

New documentation: Tutorials, Tips and Tricks

Welcome to our new area of the triple T: Tutorials, Tips & Tricks 

We have created a specific section in our documentation with tutorials, tips, recommendations and some articles so that you deepen your knowledge of Xray.

All available from within one place, easing the task of finding useful information to you.

Learn more here.

...

And more...

New Features and Bug Fixes in this release

...