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.
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.
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
Until now you had to organize your tests in Test Sets: flat, ordered lists of Tests. Test Sets can be used to group tests together in any logical way (e.g. by business case, component, etc).
The Test Repository
You can now easily create Test Executions for the failing tests, or other, from within a Test Plan.
Executions for multiple Test Environments
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.
Multiple Pre-Conditions
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.
Redesigned execution page
The execution page had a major facelift!
Our aim was to improve the overall user experience.
Since testers spend most of their time executing tests, we analyzed the process and made it more obvious and pleasant to work with.
You may notice that the "inputs" and the "output/results" of the test are now horizontally grouped. Besides that, the step status now reflects itself on the color of the step.
Agile Enhancements
From within the Agile board or in the backlog you can see the requirement status, so you're always in control.
In the Agile board, you can also see requirement's related executions, using Sub Test Executions.
Learn more here.
A Sub Test Execution has exactly the same functionalities as the Test Execution issue type. The difference between them is that the Sub Test Execution is a sub-task and can be created in a requirement's context.
Besides the direct visibility on the Agile board, creating a Test Execution as a sub-task of the requirement issue will provide the user the ability to better track time estimates.
Learn more here.
Custom Manual Test Step Statuses
Although we already supported custom test statuses, Xray now adds the ability of defining custom step statuses and their mapping to the Test status, giving you more configuration flexibility.
Learn more here.
Improved REST API
We have improved the traceability in the REST API in order to make it easier to correlate and navigate between entities.
As an example you can now easily obtain the Test Sets or Test Executions related with a given Test... or you can obtain the Test and Test Execution related with a given Test Run.
Of course, we've added specific endpoints for Test Plans.
And, in between, we have updated the whole REST API with more examples.
Learn more here.
Revamped Documentation, once again
The 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.
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 few.
We invite you to explore Xray's complete documentation starting with the Xray 3.0 Documentation Home page.
And much more...
UX & UI | Administration | Other |
---|---|---|
|
|
|
New Features and Bug Fixes in this release