Versions Compared

Old Version 1

changes.mady.by.user Sergio Freire

Saved on

compared with

New Version 2

changes.mady.by.user Sergio Freire

Saved on

Key

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


xx October March 2018

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

This version is focused on performance improvements in several areas, Test Run notifications, better navigability and enhanced UX.

The main feature of this version is the Automated Steps Library, one central place to easily manage and refactor all the Cucumber steps used in the context of a given project. Somehow related to this, edition of Cucumber Scenarios/Backgrounds is now easier mainly due to autocomplete and filtering on the steps.

But there's more, including integration with Apwide Golive, an app that leverages the power of Test Environments adding full management and planning capabilities,

As people use more and more the hierarchical test organization using 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 Cucumbera new flattened view eases the visualization and selection of Tests underneath some folder.

There 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.2.0

Note
titleRe-indexing JIRA

After installing version 3.2.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

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Column
width50%

Performance improvements

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.

Continuing our previous and on-going work, we're doing some architectual changes that will provide benefits across several different areas in future versions. Some of this improvements have been addressed in previous v3.1.x releases and v3.2.0 adds some more, including the calculation of the Test Plans overall status/progress bar, global and per-folder (in the Board).

The work we've done so far will allow us to provide additional improvements on several areas, which we'll be doing graduallyThus, 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.

Column
width50%
Image Modified

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Better navigability, enhanced UX

Automated Steps Library and enhanced edition for Cucumber Tests/Pre-Conditions


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.

Column
width40%
Image RemovedImage Removed

Image Removed Image Removed Image Removed

Column
width60%

Automation requires a lot of maintenance effort. There's the need of doing refactoring at many different levels, including at the specification level. This is even more true if you're adopting BDD and Cucumber. As your projects grow, the number of Cucumber Scenarios/Backgrounds will also increase, as will also the amount of Cucumber steps used by them.

Since (Cucumber) steps can, and shall, be used across different test specifications, you may need to do some refactoring on your existing steps in order to avoid duplicates and as means to foster reusability.

Thus, the Automated Steps Library provides one central place to see and manage all the Cucumber steps used in the context of some given project, allowing you to classify/label steps and refactor them (update, merge). You can even quickly identify the entities using those steps.

Steps are added automatically to the Automated Steps Library upon the creation/edition of Tests or Pre-Conditions. As soon as they're in the library, they can be used afterwards for easing the creation/updating of Cucumber Tests/Pre-Conditions, using autocomplete and filtering steps based on labels.

You can now be much more proeficient using the the enhanced editor for Cucumber based Tests/Pre-Condiitons, right inside Jira.


Learn more here.

Column
width60%

xxx





Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Test Run email notifications

New gadgets

Column
width60%

Two new gadgets so you can easily track your QA progress in your Jira dashboards: Requirements List Gadget and the Overall Test Results Gadget.

The Requirements List Gadget provides an enhanced list of requirements, including hierarchical information (e.g. Epic > Story), along with completeness information and respective amount of Tests, analyzed in the context of some version or Test Plan. This information is similar to the one seen at the end of the page in the Overall Requirement Coverage Report whenever drilling-down on some requirements.

The Overall Test Results Gadget provides an overall overview of the status of some Tests, in the context of a version or Test Plan. Thus, you can see the amount of Tests currently passing or failing, using a pie chart or in a table layout.


Learn more about these and all other gadgets

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.

Column
width40%

Image Removed?????

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
A bunch of hierarchical related improvements

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


Column
width50%

Image RemovedImage Removed???

Column
width50%

We know that the edition of Tests is quite dynamic; we also know that some users want to get notified upon changes of the Test/Pre-Condition specification while others don't.

Since Test cases are abstracted as Jira issues, you can also hav e

Thus, we have created a specific event that will be triggered whenever the specification of a Test/Pre-Condition is

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.



Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
TestNG support

Integration with Apwide Golive (previously Apwide Test Environment Manager)


Column
width50%

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.

Column
width50%

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Enhanced Traceability Report


Column
width100%

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.


And more...


AdministrationREST APIOther
  • 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
  • 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 for this but we kindly ask you to leave it enabled. Please read our EULA.
  • Test Statuses

  • Test Step Statuses

  • Get/Update Test Run assignee

  • Get/Update Test Run executedby
  • New branding with new logos! Hope you love it as much as we do. Please see our new website https://www.getxray.app.
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

 

Jira
serverXpand Add-ons IT Issue Tracker
columnskey,summary,type,created,priority,status,resolution
maximumIssues20
jqlQueryproject = XRAY and fixVersion = "R3.12.0" and level is EMPTY order by issuetype desc
serverIdb6309ad5-5416-33d6-9a09-a3e02f20d3e6

...