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
Using Xray	For: Manage User Acceptance Tests(UAT) Manage System Integration Test (SIT) - regression
Testing Team	-
Testing Team Organization	-
End users profile	External Contractors Non-technical internal users Internal Agile user teams
Extra details	GxP & SoX 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

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

Structure - Structure is used primarily as a requirement Hierarchy Management

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

Custom fields created:

N/A

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

Workflows:

Workflow for Test:

Xray Server + DC > Xray in Practice - Global Pharmaceutical Company > Screenshot 2025-01-30 at 16.36.03.png

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 Jan 2025)
Coverable Issues	Epic Story	→ +124k
Pre-Condition		→ +2k
Tests	Total Manual Cucumber Generic	→ +200k → +175k → +16k → +12k
Test Plan	-	→ +6.5k
Test Set		→ +2,5k
Test Execution	-	→ +33k
Sub-Test Execution	-	→ +1,8k
Test Run	-	→ +460k