You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

xx November 2017

The Xray for JIRA team announces the release of Xray 3.0.0.

This version closes the gap to enterprise test management tools and introduces hierarchical organization for Tests and goes even further.

Xray v3.0 introduces hierarchical Tests organization both at the project level, with the Test Repository, and also at Test Plan level, with the Test Plan Board.

Hierarchical Test organization can be enabled or disabled, working side by side with the other existing entities, including Test Sets.

Discover the key features below (smile)



Upgrading to Xray 3.0.0

Re-indexing JIRA

After installing version 3.0.0 of Xray for JIRA, a re-index operation of your JIRA instance is required. This is because some Xray custom fields need to be indexed in order to be searchable.


Highlights for this release

Test Repository

Xray v3.0 introduces the Test Repository concept which enables the hierarchical organization of Tests at the project level by alowing users to organize Tests in folders.

This is a different approach from the traditional way of organizing Tests in flat lists by using Test Sets, which was the only available method before Xray v3.0.

Users coming from legacy Test Management tools may find this approach more natural and intuitive. Other organizations may prefer to not enable this feature at all and choose the Test Set approach instead. There are more some pros and cons on using this kind of organization but both concepts can live together.

A new custom field "Test Repository Path" for Test issues can be included in the respective screens, to see the Test Repository folder where the Test is included in.

Learn more about the Test Repository here.



Test Plan Board


While the Test Repository concern is related with the organization of Tests in the scope of a given project during the specification phase, the Test Plan Board concern is on organization at planning level (and as consequence, at execution).

The Test Plan Board gives you the possibility to organize the Tests that are part of your Test Plan in multiple folders and sub-folders. Implicitly, you can also define the order of the Tests and the relevance of those grouped Tests (i.e. folders) by ranking them within the tree presented within the Board.

By providing you the ability to define groups and sub-groups (i.e. folders and sub-folders) for the Test Plan's Tests, you're able to track them independently and see right way their current status, even if the scope of the Test Plan is broader. You can also more easily do operations for those subset of Tests, such as creating Test Executions .

Learn more here.





Tests ranking within the Test Plan

A long awaited feature was the ability to rank Tests within the Test Plan, so it could be used to define some sort of priority for the Tests being tracked within the planned.

This ranking can then be taken into account for the Test Executions created from within the Test Plan.

Ranking of Tests in the Test Plan can in fact be done in two ways: directly in the Test Plan issue screen or in the Test Plan Board, in the case hierarchical test organization is disabled or enabled respectively. This gives users the possibility to do ranking of Tests, independently on the decision of using hierachical test organization.

CHANGE SCREENSHOT

Test Evolution Gadget


The new Tests Evolution gadget enables you to see, at a glance, the evolution/trend of the status of a group of Tests, taking into account the results of those Tests in certain Test Executions.

The calculated status (e.g. TODO, PASS, FAIL, etc) of the Tests per day is shown.

Possible usage scenarios:

  • see the progress of the calculated status of certain Tests for a specific version
  • see the progress of the calculated status of certain Tests for a specific version on a specific Test Environment
  • see the progress of the calculated status of Tests in a given Test Plan, taking into account the Test Executions associated with the Test Plan.

Learn more here.



HP ALM/QC importer


Xray v3.0 provides a basic built-in tests importer for HP ALM/QC v12.5x.

This importer is able to import test cases from HP ALM's "Test Plan" (not in any way related with Xray's Test Plan issue) by using HP ALM's REST API.

The current implementation is essentialy limited to import manual test specifications, their steps and their attachments.


Learn more here.






Revamped Documentation, once again


The documentation was completely reviewed, in terms of English spelling and also on the content being provided to you.

Some new pages worth giving a look include the whole User's Guide, How to implement QA in your projects, Advanced usage, Tips for planning tests, Using custom fields, Test Versioning, Time Tracking, Importing Manual Tests using Test Case Importer, just to name a few. Besides this, specific documentation is provided for the new features, including: Overview of the Test Repository, Test Repository, Overview of the Test Plan Board, Test Plan Board, Importing tests from HP ALM/QC.

We invite you to explore Xray's complete documentation starting with the Xray 3.0 Documentation Home page.

And more...


AdministrationJQL functionsOther
  • Greater control of who can Add Xray Issue Types in Project settings


  • Enable/disable hierarchical Test organization

  • Ability to define the project roles allowed to edit the Test Repository

  • Ability to change the Test Run's started date
  • JQL function for obtaining Tests of a Test Execution by the “executed by“
  • JQL function for obtaining tests within a Test Repository folder

  • JQL function for obtaining tests within a Test Plan Board folder
  • Test Set filter in Test Execution screen shows only relevant Test Sets


  • Xporter improvements related with exposing info about Xray attachments on Tests and Test Runs


  • Test Case Importer
    • Comments
    • DateTime fields
    • Test Repository folder (for existing folders)


  • Inherit dates for planned Test Executions, from the Test Plan

  • Ability to change the Test Run's started date

New Features and Bug Fixes in this release

 

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh


  • No labels