Versions Compared

Old Version 1

changes.mady.by.user Helder Ferreira

Saved on

compared with

New Version 2

changes.mady.by.user Helder Ferreira

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width80%

April 14th, 2023

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

This version features Dynamic Test Plans, an improved way to define a Test Plan by defining a saved filter as the source of Tests for the Test Plan. This way, all Tests on the filter will be added automatically into the Test Plan. 

Column
width20%

Table of Contents

Upgrade Notes

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderStylesolid
Section
Column
width33%

Upgrading Xray to 6


Expand
titleUpgrading 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
titleUpgrading from versions 3.2.x and 3.3.x

If upgrading from v3.2.x or v3.3.x to v6, 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
width33%

Downgrading from Xray 6


Expand
titleDowngrading to any version

Downgrading from Xray 5.x.x to a previous version will have the following side effects on 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;
  • 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
  • Test Run Page
    • The Merge/Reset action will be displayed
Expand
titleDowngrading 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.

Expand
titleDowngrading 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
borderWidth1px
Section

Dynamic Test Plans

Column
width40%


Column
width60%


This highly requested Xray Enterprise feature allows users to create and keep their test plans updated seamlessly.

Configure Test Plan with Saved Filter


One 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.





Just one more, yet important, thing...

Documentation is always important, and sometimes you may miss it.

This time we added some process-related articles detailing how to integrate and perform exploratory testing with Xray and some ideas on implementing acceptance criteria and tracking related testing results.


Here's a summary of all the relevant articles that we've added and updated recently:


All New Features and Bug Fixes in this release

 

Jira
serverXpand IT Issue Tracker
columnIdsissuekey,summary,issuetype,created,priority,status,resolution
columnskey,summary,type,created,priority,status,resolution
maximumIssues50
jqlQueryproject = XRAY and fixVersion = "6.5.0" and level is EMPTY and issuetype not in subTaskIssueTypes() order by issuetype desc
serverIdb6309ad5-5416-33d6-9a09-a3e02f20d3e6