This document provides an overview of how to leverage the Xray test management application for Jira. Some key points covered include: 1. Xray allows for both scripted and exploratory testing approaches to be combined and consolidated. 2. Core concepts of Xray include organizing tests, planning test execution, and providing test coverage visibility and traceability. 3. Xray leverages existing Jira features for permissions, workflows, custom fields and screens to manage the entire testing process.

1. Leveraging the power of
your testing with Xray
Sérgio Freire
Solution Architect &
Testing Advocate
@XrayApp
@darktelecom

2. Takeaways
• Understand the core concepts of Xray
• Quickly understand how coverage works and how you can use it to your advantage
• How to integrate test automation with Xray
• How to combine and consolidate scripted testing with exploratory testing
• Understand some of the built-in capabilities that allow you to tune your testing process to
your team needs
2@darktelecom

3. Xray Overview

4. Recap: Testing approaches/styles
4
Test automation
Test cases Exploratory
testing
Scriptedtesting
@darktelecom

5. What is Xray?
• Scripted and Exploratory Testing
• Test Management App for Jira
• Cloud, Server and Data Center
• Organize, Plan & Execute Tests
• Report bugs
• Test Coverage visibility
• Complete traceability
• REST API
• Automation friendly
• Customization friendly
5@darktelecom

6. Issue types for different testing phases
Test and
Pre-Condition
Test Set
Test Execution
Sub-Test Execution
Test Plan
Specify
Organize
Plan
Execute
1. Leverages Jira’s built-in features
2. Permission control
3. Implementation of Workflows
4. Custom fields
5. Screens customization
6. Assignment, Changes tracking
7. Collaboration
8. Use other 3rd party Jira apps
9. And much more…
Leveraging the advantages of Jira issues
6
(and Test Repository)
(and Test Run)
(and its Board)
@darktelecom

7. Concepts

8. “”
Story(ies) Epic(s)
Story(ies)
other issue types to
be handled as such
Requirements: issues coverable with Tests
Software Requirements as defined by IEEE
• A condition or capability needed by a user to solve a
problem or achieve an objective
• A condition or capability that must be met or possessed by
a system or system component to satisfy a contract,
standard, specification or other formally imposed
documents
• A documented representation of a condition or capability
as in 1 and 2.
In sum, Requirements are intended to facilitate a shared
understanding of what needs to be built.
8@darktelecom

9. EnvironmentsVersions
CoverageTest Plans

10. Project
Version(s) / Release(s)
“requirements”
(i.e. issues coverable with Tests)
Test(s)
Test Plan(s)
Test(s)
Test
Execution(s)
iterations
PlanningCoverage
10@darktelecom

11. Project
Version/Release or Sprint
Test Plan
(NRT)
Test(s) Test Execution(s)
Test Plan
(RT)
Test Plan
(automation)
Test Plan
(security)
Test Plan
(performance)
iterations
Planning context
One or more Test Plans per “context”, depending:
• If you want to manage & track test progress
independently
• If each Test Plan lifecycle is independent
• If you want to assign each plan to different teams
• If you want to clear distinguish the results from different
tests, because they, for example, bring different value
Test Planning
11@darktelecom

12. Xray live

13. Project CALC
Math
operations
Epic
Sum
Story
Login
Story
Manual
scripted test
v1.0
Cucumber
Scenario
Usability
exploratory
test
Robot
Framework
tests
Sprint 1
Test
Execution
Test Plan
JUnit Java
tests
Manual
Precondition

14. Xray Exploratory App
14
xr4y.io/explore

15. Thank you!
sergiofreire.com | @darktelecom
(images from Unsplash and contributors)