28 March 2018
The Xray team is proud to announce the release of Xray 3.1.0.
This version is focused on performance improvements in several areas, Test Run notifications, better navigability and enhanced UX.
Xray v3.1 also further improves the Test Repository and the Test Plan Board, introduced with Xray v3.0.
But there is much more, including great improvements for automation with the additional support for TestNG along with some enhancements for Cucumber.
Discover the key features below
Upgrading to Xray 3.1.0
After installing version 3.1.0 of Xray, a re-index operation of your Jira instance is required. This will enable Xray custom fields to become searchable.
Downgrading from Xray 3.1.x
Xray v3.1 introduces the ability to configure and rename the issue link (e.g. "Tests") used for relating Tests with requirements. Therefore if you change it, including the outward and inward descriptions, if you decide to rollback to then Xray will create the "Tests" issue link with the default outward and inward descriptions (i.e. "tests" and "tested by", respectively). You may overcome this, by renaming the issue link to its defaults before downgrading.
Xray v3.1 introduces several performance improvements in several reports, including the Traceability Report and the Test Plans Report, and also in some gadgets.
Besides this, some measures were taken in order to avoid "messy", by default settings in the Test Runs Summary and Test Runs List gadgets that could cause some performance hits.
Thus, gadgets now require that you specify a filter with the issues that should be considered for its source data.
Improving performance is an on-going effort, so expect additional enhancements to come in future versions.
Better navigability, enhanced UX
Within Test Execution and Test Plan issues, now you can jump to a filtered list of the related Test issues right from the Overall Execution Status bar. You just need to click on the numbers specific to each status.
Most of the numbers shown in "Test Executions Report", "Test Plans Report" and in the "Overall Requirement Coverage Report" (in the drill-down of a bar chart) are now links to the related issues.
Test Runs shown in the "Test Runs List" gadget, in the Test Runs Report and in the Traceability Report now provide a link to the details page (i.e. the execution screen).
The execution screen provides also links to the related Test Plan(s), so you quickly jump to it.
In the Test Execution issue screen, you can now select all Test Runs or several of them, independently of the page that you're looking at. This enhances a lot bulk operations.
Learn more here.
Test Run email notifications
A long-awaited feature are Test Run email notifications.
Now you can get notified or notify any relevant stakeholders whenever a Test Run is assigned, when its status is changed or even if the precedent Test Run has been "finished".
Test Run notifications reuse Jira's notifications mechanism, using events and notification schemes. This makes the notification mechanism quite powerful and seamless to setup for Jira administrators.
Learn more here.
A bunch of hierarchical related improvements
In the Test Repository and in the Test Plan Board it's now possible to use a context action over a selected folder, or over some selected Tests, to view the related Test issues in the Issues search page, therefore enabling you to obtain the relevant Tests and do operations with them, if needed.
By the way, moving Tests to the Orphans meta-folder is as simple as using drag&drop.
You can now create Test Executions from the Test Plan Board and inherit, by default, the planning dates.
Also in the Board, creating Test Executions for Tests currently in some status, for a specific Test Environment, can now be done using the "Create Test Execution" over some folder.
Cloning Tests and Test Plans will also clone the related hierarchical information with them:
- whenever cloning and/or moving a Test to some other project, the folder is also created in the destination Test Repository.
- whenever cloning Test Plans, the Board information (i.e. the folder structure) is also cloned.
Learn more here.
A long awaited feature by Java teams was adding support for TestNG.
Now you can submit results from TestNG tests and get visibility of them in JIRA and in the related requirements.
Similar to what is provided for other formats, two REST API endpoints for TestNG are now provided.
We also provide a tutorial, Testing using TestNG in Java, so you can see how it works with a real example.
Learn more here.
Enhanced Traceability Report
Besides performance improvements on this report, you may now see the hierachical information of parent and sub-requirements (up to two levels).
So, if you have an Epic some related Story issues, you will be able to see their relation in the report and evaluate the traceability information for the Epic and also for each individual Story.
Besides this, we added built-in capabilities to make the Traceability Report now exportable to CSV, and include this hierarchical information of course.
- Test Run Notifications related settings
- Test Repository related endpoints for CRUD folder operations
- Test Repository folder structure
- Pre-Conditions associated with a given Test
- Test Case Importer is now available for standard users, as long as they're able to create issues and do bulk changes
- Ability to create folders in the Test Repository, whenever using the Test Case Importer
- Make Cucumber import idempotent (no duplication of Tests/Pre-Conditions)
- (experimental) Support for using the source code version control system (e.g. Git) as the master of features and related Scenarios. More info here.
- A new column named "Steps Progress" can be added to Test Runs sections (e.g. in the Test Execution issue screen) for showing the progress of step execution
New Features and Bug Fixes in this release