Upgrade Notes
Upgrading Xray to 6
Downgrading from Xray 6
Release highlights
Modular Test Design
Modular test design is a way of promoting test case reusability and composition across a large test repository. In order to design modular tests, you can create a test where some steps call or include other test cases. This prevents testers from having to write the same steps over and over again in different high-level tests.
Using a modular design approach, any test becomes a building block of more extensive test scenarios. Still, they can also be executed individually if needed.
A common use case for modular tests is end-to-end testing. End-to-end tests often need to pass through the same area or component of the application before asserting the final result. With modular test design, you can reuse the tests for these common areas or components.
Find out more about this feature here.
Quickly create executions for failed tests from a requirement issue
We have added a new option that allows users to create new Sub-Test Executions (or Test Executions) for tests in a specific status from the requirement issue screen.
A common usage scenario is to create a new Sub-Test Execution for all failed tests within a Story.
Learn more here.
Importing screenshots from Robot Framework
When executing Robot Framework tests, we can capture screenshots after executing certain steps and include them in the execution report.
These screenshots will now be imported by Xray and will be provided on the execution screen as evidence of the execution.
Learn more about this feature here.
And more...
UI/UX Improvements
- XRAY-2865: As a user, I can view the user's display name in the Test Runs report
REST API
- XRAY-3692: Test repository REST API folder call
JQL functions
- XRAY-2552: As a user, I can filter obtain a list of Tests based on the Test Run fields from a Test Execution using a JQL function
Configuration
- XRAY-8073: The Test Evolution gadget limit should be defined by the admins
All New Features and Bug Fixes in this release