Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The main feature of this version is the Automated Steps Library, the central place to easily manage and refactor all the Cucumber steps used in the context of a given project. In addition, autocomplete and filtering on the steps make editing of Cucumber Scenarios/Backgrounds easier.

We also included integration with Apwide Golive, an app that leverages the power of Test Environments.

As people use more and more the hierarchical test organization using the Test Repository and the Test Plan Board, a new flattened view facilitates the visualization and selection of Tests.

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.

As part of our continuous improvement, more performance improvements landed in this version, for the most intensive gadgets/reports and JQL functionsThere are also improvements in the HP ALM/QC migration tool, several architectural changes for increased performance and much more.

Discover the key features below (smile)


Table of Contents

Image Modified

Upgrading to Xray 3.3.0

From Xray After installing version 3.23.0 , the amount of information indexed by Jira's Lucene framework has increased. In order to not increase the index time, Xray is now pre-calculating this data so when re-indexing there is less calculation to be done.Whenever installing Xray 3.2.0 the first time, this implies that an upgrade task must 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. However, this process may be long and heavy depending on the Jira instance size and thus we recommend to perform the upgrade at off peak times.

In order to manage this calculation, Xray provides a panel inside "Custom Field" preferences page from where you can stop, start and follow progress of it.

Image Removed

After installing version 3.2.0 of Xray, if you upgrade from a version less than 3.2, a re-index operation of your Jira instance is required so that the internal data becomes searchable and usable by Xray. Otherwise, if you upgrade from v3.2.x to v3.3.y, no re-index should be needed.


Downgrading from Xray 3.3.x

Downgrading from Xray 3.3.x to a version less than 3.2.x 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.

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Performance improvements


Column
width50%

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 improved performance on:

  • Test Lists gadget;
  • Overall Requirement Coverage gadget & report;
  • Historical Requirement Coverage gadget & report;
  • requirements() and requirementsWithStatusByTestPlan() JQL functions
We're doing ongoing architectural changes that will provide performance benefits across several different areas in future versions. Version 3.2.0 adds some improvements, including the calculation of the Test Plans overall status/progress bar, global and per-folder (in the Board)
  • .


Improving performance is an ongoing effort, so expect additional enhancements to come ahead.

Column
width50%
Image Modified

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

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


Column
width50%

Column
width50%

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.

...

Maximum selectable Test Runs for bulk operations. Read more here.
  • Metrics: Xray now collects some anonymous usage metrics (e.g., counters) that will allow us to improve Xray for all of you. You can opt-out of this, but we kindly ask that you leave it enabled. Please read our Privacy Policy.
  • Xray JSON Multipart
    Test Statuses
    Test Step Statuses
    Get/Update Test Run assignee
  • Get/Update Test Run executed by
  • AdministrationREST APIOther
    • Maxid

    • 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
    • HP ALM/QC Importer:
    • support for HTTPS
    • ability to create folder structure in the Test Repository
    • ability to specify the base folder from where Tests will be imported from
      New branding with new logos. Hope you love it as much as we do! Please see our new website https://www.getxray.app.

    New Features and Bug Fixes in this release

    ...