Workshop 5

Xray and JIRA automation

 Introduction
This presentation will be split into the following areas:

Xray
JIRA automation

Data
 Introduction
You can make your own test JIRA. Please do NOT use your work
email.

https://www.atlassian.com/

For this presentation, the following instance is set up

https://xraydemot17.atlassian.net/
 Xray
Guides

https://docs.getxray.app/category/xc

https://academy.getxray.app/
 Xray
All functionality is based on issue types which means things like
automation and filters will work with them.

• Test: Used to define test cases of different types that can be

executed multiple times using Test Execution issues.

• Precondition: Used to abstract common actions that must be

ensured before the test case execution. A Precondition can be
associated with multiple test cases.
 Xray
• Test Set: Creates a group of test cases. Used to associate all
included Tests with other Xray issue types like Test Execution and
Test Plan. A Test Set can also be associated with a requirement
issue to provide coverage and test status.

• Test Plan: Used to define the scope of test cases for a given test
campaign and to aggregate all executions for those tests
displaying the latest result for each test case.
 Xray
• Test Execution: Used to execute test cases already
defined.

• Sub Test Execution Used to execute test cases already

defined. A Sub Test Execution can be created for a parent
issue like a requirement in order to execute the test
cases associated with it.
 Xray How to Test
Step 1: Create a Test, these tasks
contain the instructions and any
other information required to
complete a test. It is important to
note that the Test tasks are the
templates and the version to be
worked on by Testers.

They can contain any number of

steps, the steps are the actions to
execute.
 Xray How to Test
Step 2: Manage your Tests
On the testing board, you can see all Tests for a project, they can be
organized in a folder and grouped as needed.
 Xray How to Test
You can also use Test sets to group Tests. This is a separate issue type
that makes running Test executions easier.
 Xray How to Test
Step 3: Create a Test execution.
The Test Execution task is the
one Analyst will work on and
that contains the pass and fail
information. Both Test Sets and
Tests can be right clicked in the
Testing board to select create
Test execution.
 Xray How to Test
Step 4: Complete actions for Test
execution. This is the actual
testing part where the
instructions are followed and
the results are recorded.
 Xray How to Test
There are some features that make testing easier.

Parameterized testing
Import of tests
Coverage and Preconditions
 Xray Data
One of the main advantages of Xray is the ability to gather more
data easily and link defects with the tasks that found them.

Test Coverage Report

Traceability Report
Tests List Report
Test Sets List Report
Test Executions List Report
Test Plans List Report
Test Runs List Report
Test Plans Metrics Report
 Xray Dashboards
Overall Test Coverage
Tests List Gadget
Test Sets List Gadget
Test Execution List Gadget
Test Plans List Gadget
Overall Test Results Gadget
Tests by Test Type Gadget
Requirements List Gadget
Test Runs List Gadget
Test Runs Summary Gadget
 JIRA automation
JIRA comes with build in automation

Guide
https://www.atlassian.com/software/jira/guides/automati
on/tutorials#manage-automation-rules
 JIRA automation
What are triggers?

Every rule starts with a trigger. They kick off the execution
of your rules. Triggers will listen for events in Jira, such as
when an issue is created or when a field value is changed.
You can also trigger rules to run from third party services
like Bitbucket or GitHub.

Triggers can be set to run manually, based on a condition

you set or schedule
 JIRA automation
What are conditions?

Conditions allow you to narrow the scope of your rule.

They must be met for your rule to continue running. For
example, you can set up your rule to only escalate an issue
if it is high priority.

If a condition fails, the rule will stop running and no

actions following the condition will be performed.
 JIRA automation
What are actions?

Actions are the doers of your rule. They allow you to

automate tasks and make changes within your site. They
allow you to perform many tasks, such as editing an issue,
sending a notification, or creating sub-tasks.
 JIRA automation
What are actions?

Actions are the doers of your rule. They allow you to

automate tasks and make changes within your site. They
allow you to perform many tasks, such as editing an issue,
sending a notification, or creating sub-tasks.
 JIRA automation
What is branching?

Issues in Jira rarely exist in isolation. This means that when using
automation, actions often need to apply, not only to the source
issue that triggered the rule, but also to any issues that are related
to the source issue.

Special conditions and actions are available to create powerful

rules that can work across complex issue relationships. For
example, checking that all sub-tasks of a parent issue are resolved.
 JIRA automation
What are smart values?

Smart values allow you to access and manipulate a wide range of

issue data within your site. They can add significant power and
complexity to your rules. For example, the smart value
{{now.plusDays(5)}} references the current time and adds 5 days
to it, while {{issue.summary}} will print off the summary of the
issue.
 JIRA automation
What are smart values?

Smart values allow you to access and manipulate a wide range of

issue data within your site. They can add significant power and
complexity to your rules. For example, the smart value
{{now.plusDays(5)}} references the current time and adds 5 days
to it, while {{issue.summary}} will print off the summary of the
issue.
THANK YOU