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 | Pharmaceutical |
|---|---|
| Using Xray | Xray DC since 2021 |
For:
| |
| Testing Team | - |
| Testing Team Organization | - |
| End users profile | External Contractors Non-technical internal users Internal Agile user teams |
| Extra details | GxP & SOC complaint company An internal team produces videos, how tos and other resources to help teams understand testing practices. |
Xray Features highlights
In this use, the customer takes advantage of:
- Test Case Importer
- Doc Generator - Requirement Traceability Matrix
Team choice for the top Xray Feature
The most important feature Requirement Traceability Matrix, as they use it as a go-to document for validation and approvals due to its GxP and SoX compliance.
Integration with other tools
Xray Configuration & Customization
Xray Project Organization
- All-in-one - Requirements, Tests & results are managed in the same project
Test Status created
- OUTOFSCOPE - final status defined as OK to identify tests that are out-of-scope and should not affect negatively the requirement
- QUALIFIED-AS-PASS -final status defined as OK to identify tests that are out-of-scope and should not affect negatively the requirement
Fields in use
→ Labels: Used to differentiate internal teams Test Run assignment
→ Fix Version: is Used to document, release number / Phase / Team
→ Test Environment: is used to document, release, production env, OS environments, OS Builds
Testing Practices Details
Writing Tests
- Tests are created mainly through importing by using Test Case Importer.
Planning & Organization Tests
- Heavily use of Test Repository
- Test Plans are created per Release (when applicable, one for User Acceptance Tests and other for System Integration Tests)
Executing Tests
- Test executions are created per user ( each tester as their own test executions) per sprint - usually more than 20 Test Executions per Sprint
- In other projects, the test execution is created per sprint ( agile teams work on the same executions and organize it by labels)
Analysing Results ( Reports)
| Report | Used for |
|---|---|
| Traceability Report | To analyse coverage |
| List Xray entities ( Gadgets) | Daily Monitoring |
| Requirement Traceability Matrix (Doc Generator) | Export information for compliance purposed Export information in report to Release Approval |
Facts - Xray Coverable Issues & Entities
| Issue/Entity | Details | Some numbers (last updated at Jun 2024) |
|---|---|---|
| Coverable Issues | Epic Story | - |
| Tests | Total Manual Cucumber Generic | > 150 000 > 130 000 > 10 000 > 7 000 |
| Test Plan | - | > 4000 |
| Test Execution | - | > 26 000 |
| Sub-Test Execution | - | > 4 000 |
| Test Run | - | > 300 000 |