This implies that an upgrade task will run to map the oldest test types for the new kind. This one-time action will run in the background so that Xray remains available during the upgrade. A re-index operation of your Jira instance is required to make the internal data searchable and usable by Xray.
Note
Test Types
Xray supports the followingkindsof Tests:
Steps- defined with an ordered list of steps. Each step contains the action and the excepted result along with other fields.
Gherkin- defined using theGherkinlanguage for BDD.
Unstructured- defined with a single text field without any enforced structure.
When Xray is first installed, oneTest Typeis installed for each Testkindthat Xray supports:
Manual (Steps kind)
Cucumber (Gherkin kind)
Generic (Unstructured kind)
Column
width
33%
Downgrading from Xray 7.6.0
Expand
title
Downgrading to any version
Downgrading from Xray 7.x6.x 0 to a previous version may have the following side effects:
After creating some specific data using Test Case Versions, the user may have some glitches when downgrading to a specific version of Xray
Until Xray 7.6.0, Xray DC only supported the Test types below
If you create a new Custom Type and map it to a Kind, when downgrading, Xray will not know about this mapping and will assume it is an Unstructured Test.
On a Test Issue, multiple manual test versions with steps, when downgrading the test issue will show all steps from all the versions
On a Test Issue, multiple manual test versions with specific datasets, when downgrading the test issue will show the parameters from all the datasets
On a Test issue, having different test versions linked to the same precondition issue when downgrading, the test issue will show an integrity error instead of showing the precondition table Image Removed And the precondition will show the warning of being linked to an archived test Image Removed
For example, you create a Type called "Hierarchical Steps" and map it to the Kind Steps. When downgrading, the testers will see the Xray UI of an Unstructured Test. When changing the Test type to Manual, the data and correct UI will be shown.
Release highlights
Panel
borderColor
#F3F3F3
bgColor
#FAFAFA
borderWidth
1px
Section
Test Case Versioning
Column
width
40%
Column
width
60%
This highly requested Xray Enterprise feature allows users to create and manage multiple versions of the same test case, to easily track and revert changes in your test specification.
Why Test case versioning?
Test cases are not static. They evolve when requirements change, or improvements are made to the application under test. Although Xray logs test specification changes in the Jira history, it is not easy to revert to a specific test case version. With Test case versioning, you can now:
Create a new version of a test case with a single click
Compare different versions of a test case and see what has changed
Restore a previous version of a test case if needed
Assign a test case version to a test execution or a test plan
Track the test execution results for each test case version
Mark specific milestones of the Test with versions
Have multiple active versions simultaneously,even of different Test Types, as you can execute them all independently.
How does Test case versioning work?
Test case versioning works in the same way as versioning of other issue types in Jira. Since Xray's Tests are Jira issues, we follow the same approach so your users work in the same manner they already do.
To create a new version of a test case, you just need to click on the "Create new version" button on the test issue screen.
Test case versioning is a powerful feature that can help you manage your test specification more efficiently and effectively. It is available for Xray Enterprise customers only.
If you want to learn more about Test case versioning, please visit our documentation pagehere.