Test

Until now you had to organize your tests in Test Sets. And that makes all sense.

But one thing is organizing the tests, by grouping them, and another thing is planning tests for a given release.

With Xray 2.0 we've introduced the Test Plan, so you can create and manage your tests effectively. Assign one, or more, Test Plans to a given release and track progress of the tests within each Test Plan.

You can even see the requirement coverage taking into account the Test Plan tests.

Repository

Xray v3.0 introduces the Test Repository concept which enables the hierarchical organization of Tests at the project level by allowing 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 continue using the Test Set approach instead. There are more some pros and cons on using this kind of organization, but both concepts can exist side-by-side.

A new custom field Test Repository Path for Test issues can be included in the respective screens to see the Test Repository folder to which the Test belongs.

Learn more about the Test Repository hereYou can now easily create Test Executions for the failing tests, or other, from within a Test Plan.

Image RemovedImage Added

While the Test Repository addresses the organization of Tests within the scope of a given project during the specification phase, the Test Plan Board does it at the planning level (and as consequence, at execution).

The Test Plan Board enables you 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 away their current status, even if the scope of the Test Plan is broader. You can also more easily do operations for those subsets of Tests, such as creating Test Executions

The Test status was calculated by looking at the test's last execution. But this does not work well if you execute the same test in two different devices and you want the status to be like a "merge" of the two results.

Within a Test Execution you can now specify the Test Environment(s) where the tests will be executed. A Test Environment is similar to a label, but Xray provides some special logic to deal with it. Let's say that you have executions for three Test Environments: "Chrome", "Safari" and "Firefox". The test is considered as PASS only if the latest executions for Chrome, Safari and Firefox are all PASS; it will be FAIL if any of them has failed.

Learn more here.

A long-awaited feature is the ability to rank Tests within the Test Plan, so it could be used for Test prioritization.

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

Ranking of Tests within the Test Plan can be done in two ways: directly in the Test Plan issue screen (if hierarchical test organization is disabled) or in the Test Plan Board (if hierarchical test organization is enabled). This means you can rank Tests, whether you use hierarchies or not.

Xray supports, since day one, Pre-Conditions as a way to define initial conditions that should be met before executing a Test. This is very useful whenever you have to start by doing exactly the same thing in your tests. But sometimes you have to do several things  (e.g. restore DB, authenticate) before your Test steps.

Each of those things may be used independently (e.g. some Test may require just to restore the DB, another may require just to authenticate, and others may require that both things, or even more, need to be done before starting executing the steps).  Now you can assign multiple Pre-Conditions to a given Test. 

Image Removed

Image Added

The entire documentation was completely reviewed , we

reorganized and is now more extensive and detailed in many areas. We have added many diagrams to make things clearer.

for form and clarity, and was also expanded in terms of content.

Some new Some pages worth giving a look include the whole : User 's Guide, Project Organization, Test Process, Terms and Concepts, Examples of Reports built with Xporter, Examples of custom gadgets, FAQ, just to name a fewGuide, 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, among others.

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.

New tutorials covering integration with Micro Focus' UFT Pro (LeanFT) are provided: Testing using UFT Pro (LeanFT) and JUnit in Java, Testing using UFT Pro (LeanFT) and NUnit in C#.

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