The current Use Case is from an existent Xray Customer. Please do not use it as a standard approach or interpreted as the "right way" to use Xray. Xray is a flexible tool and should be adapted to your own use case. Be inspired. |
Content
Team Profile
| Industry | Food Retail and Distribution |
|---|
| Using Xray | Xray Cloud since 2023 |
|---|
For: - Testing new features
- Validate requirements
|
| Testing Team | - |
|---|
| Testing Team Organization | There’s no specific QA team. |
|---|
| End users profile | Product Owners |
|---|
| Extra details | - |
|---|
Xray Features highlights
In this use case, the customer takes advantage of:
- Xray being seamlessly integrated with Jira, in particular, uses Jira Workflows to manage and control Xray Entities
- Configuration restrictions applied to workflows to guarantee permission control
- Xray Exploratory App seamlessly uploading Exploratory Testing in Xray
Traceability has been named the most valuable feature as it ensures a clear view on links between requirements, test cases, executions and defects and this is vital for retail companies due to the fast-paced and high-stakes nature of the industry. - Ensures alignment with strict regulations by providing a clear audit trail for sensitive data and transactions.
- Prevents disruptions by ensuring systems like inventory and pricing engines are thoroughly tested.
- Helps to validate features such as online purchases, payment gateways, and loyalty programs for reliability.
Xray Traceability Report is key to reduce the chance of deploying faulty features, mitigating risks like pricing errors or failed transactions. |
Integration with other tools
- ServiceNow is used to map specific service requests directly to Jira requirements or tasks, creating a 1-1 relationship between the two. This integration allows for clear traceability, enabling the team to quickly identify which features or functionalities will be impacted if bugs are detected during the development or testing stages. The synchronization of updates and test execution results ensures seamless collaboration between teams and accelerates issue resolution.
Xray Configuration & Customization
Xray Project Organization
- Test Repository Project which consists in a centralized storage for managing and organizing reusable test cases efficiently.
- Specification Project which is focused on defining and managing requirements while ensuring traceability to tests.
- Testing Project being the dedicated space for executing tests, managing cycles, and reporting results with real-time visibility
The project organization reflects an approach Dedicated Test Repository .
Test Status created
- Aborted
- Pending 3rd
- Blocked
- For Testing
Custom fields created:
Workflows
Workflow for Tests
Workflow for Bugs (IT)
When a Test reaches the “Testing” phase and fails, a Bug is generated, and the process transitions to “Ready for Testing.” Subsequently, an Execution is created immediately.
Workflow for Defects (UAT Phase)
When a test moves to “Ready for approval” and fails thereafter, a “Defect” is created and follows the below workflow.
Testing Practices Details
Writing Tests
A centralized Test Repository serves as a hub where all tests are created.
Product Owners have the flexibility to design tests as needed, tailoring them to their specific requirements.
Planning & Organization Tests
- Tests are typically structured within folders in the Test Plan Board.
- Test Sets are rarely utilized, as organization primarily revolves around Test Repository.
- Test Plans are created per Sprint or Release to align with delivery cycles.
Executing Tests
- Test Executions are derived directly from Test Plans, providing a structured execution framework.
- Sub-Test Executions are commonly used for managing and addressing Bugs, which are treated as coverable issue types.
Analysing Results ( Reports)
| Report | Used for |
|---|
| Test Runs Summary Gadget | Filtered by the active Test Plan to monitor execution progress, identify bottlenecks in status, and facilitate load balancing among assigned users. |
Facts - Xray Coverable Issues & Entities
For this specific use case with was not possible to collect Xray entities use statistics. |
| Issue/Entity | Details | Some numbers (last updated at Oct 2024) |
|---|
| Coverable Issues | Feature (Custom) Story Requirement (Custom) Bug | - |
 Pre-Condition
| | +300 |
 Tests
| Total Manual Cucumber Generic | + 10k + 8k + 1k + 50 |
 Test Plan
| - | +170 |
 Test Set
|
| +300 |
 Test Execution
| - | +3000 |
Sub-Test Execution | - | +500 |
| Test Run | - | - |