The Xray team is proud to announce the release of Xray 7.0.0.
This version features Test case versioning for Xray Enterprise, test cases evolve when requirements change, or improvements are made to the application under test. Although Xray logs test specification changes in the Jira history, it is not easy to revert to a specific test case version. With Test case versioning, you can now create multiple versions of the same test.
Column
width
20%
...
Panel
borderColor
#F3F3F3
bgColor
#FAFAFA
borderStyle
solid
Section
Column
width
33%
Upgrading Xray to
6
7
Expand
title
Upgrading from versions < 3.2.x
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 one-time action will run in the background so that Xray remains available during the upgrade. A re-index operation of your Jira instance is required to make the internal data searchable and usable by Xray.
Note
Please be aware that this upgrade task will run immediately after updating Xray. As this operation can take some time and use a considerable amount of server resources, we suggest scheduling the upgrade of Xray outside of business hours. It is always possible to cancel the recalculation operation in the Xray configuration section → Custom Fields → Maintenance.
Expand
title
Upgrading from versions 3.2.x and 3.3.x
If upgrading from v3.2.x or v3.3.x to v6v7, 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 the Lucene indexes.
Note
As this operation can take some time and use a considerable amount of server resources, we suggest scheduling the upgrade of Xray and recalculating the custom fields outside of business hours.
Column
width
33%
Downgrading from Xray
6
7
Expand
title
Downgrading to any version
Downgrading from Xray 57.x.x to a previous version will may have the following side effectson Test Runs with a dataset:
Test parameters will no longer be converted on the Test Run page; this includes Test Step definitions and Pre-Conditions;
When loading a Test Run created on version 5.x.x, the merge/reset message will be displayed;
When merging a Test Run created on version 5.x.x with the new Test Step definition, all Test Step results will be updated but the reset/merge message will still be displayed;
A Test Run created on version 5.x.x with iterations will be displayed in a "flat mode." The iterations will no longer be available and all the Test Step results from each iteration will be presented in the Test Steps section; Image Removed
After the downgrade, the integrity checker will fail on "Check for invalid Mementos" for all Test Runs created on version 5.x.x. We recommend running the integrity checker before downgrading to eliminate possible invalid mementos.
Downgrading from Xray 6.x.x to a previous version will have the following side effects:
Test Issue:
A Call Test will be converted to a regular test step with a warning message Image Removed
Test Run Page
The Merge/Reset action will be displayed
Expand
title
Downgrading to versions ≤ 4.1.x
The Test Step Custom Fields and Test Run Custom Fields of the type "User Picker" must be deleted in the project configuration as they are not supported. Following that, the Test Runs that are using a User Picker field will have to be merged or reset. This includes Test Runs with the field for the Test Run itself and Test Runs for Manual Tests where the Test Steps contained the User Picker field.
After creating some specific data using Test Case Versions, the user may have some glitches when downgrading to a specific version of Xray
On a Test Issue, multiple manual test versions with steps, when downgrading the test issue will show all steps from all the versions
On a Test Issue, multiple manual test versions with specific datasets, when downgrading the test issue will show the parameters from all the datasets
On a Test issue, having different test versions linked to the same precondition issue when downgrading, the test issue will show an integrity error instead of showing the precondition table
Image Added And the precondition will show the warning of being linked to an archived test Image Added
Expand
title
Downgrading from any version
Downgrading from Xray 6.x to a version less than 3.2.0 implies performing a re-index afterward. This is because from Xray 3.2.0 onwards, the content and format of what Xray indexes have changed.
Historical Coverage Gadget
Some configuration parameters for this gadget were modified due to supporting multiple projects using a saved filter as a source. It is possible that some users will get errors on the gadget after downgrading from 4.x. If this happens, please edit the configuration to ensure the gadget is configured properly.
Release highlights
Panel
borderColor
#F3F3F3
bgColor
#FAFAFA
borderWidth
1px
Section
Dynamic
Test
Plans
Case Versioning
Column
width
40%
Image RemovedImage Added
Image RemovedImage Added
Column
width
60%
This highly requested Xray Enterprise feature allows users to create and keep their test plans updated seamlessly.
Configure Test Plan with Saved Filter
users to create and manage multiple versions of the same test case, to easily track and revert changes in your test specification.
Why Test case versioning?
Test cases are not static. They evolve when requirements change, or improvements are made to the application under test. Although Xray logs test specification changes in the Jira history, it is not easy to revert to a specific test case version. With Test case versioning, you can now:
Create a new version of a test case with a single click
Compare different versions of a test case and see what has changed
Restore a previous version of a test case if needed
Assign a test case version to a test execution or a test plan
Track the test execution results for each test case version
Mark specific milestones of the Test with versions
Have multiple active versions simultaneously,even of different Test Types, as you can execute them all independently.
How does Test case versioning work?
Test case versioning works in the same way as versioning of other issue types in Jira. Since Xray's Tests are Jira issues, we follow the same approach so your users work in the same manner they already do.
To create a new version of a test case, you just need to click on the "Create new version" button on the test issue screen.
Test case versioning is a powerful feature that can help you manage your test specification more efficiently and effectively. It is available for Xray Enterprise customers only.
If you want to learn more about Test case versioning, please visit our documentation pageOne of the features of a Test Plan is that it allows you to add tests in different ways. In addition to being able to add tests to the Test Plan explicitly, you can now use a filter and define a custom JQL depending on your needs so that tests will appear automatically on the Test Plan. A filter is a predefined set of criteria that selects tests based on certain attributes, such as status, priority, assignee, or label. A custom JQL query language lets you write more complex and flexible conditions to select tests based on any field or property. Using a filter or a custom JQL saves time and effort in adding tests to the Test Plan and ensures that your Test Plan is always up-to-date with the latest changes in your test cases. Learn more here.