Test Management for JIRA
Agenda
o What is “Xray”?
o Requirements and Defects
o Xray Issue Types
o Project Configuration for Test Management
o Reports
Overview
o A complete Test Management tool for Jira.
o Xray supports the entire testing life cycle:
➢
Test Planning
➢
Test Design
➢
Test Execution
➢
Test Reporting
o Xray supports both manual and automated tests, including
full support for Cucumber tests in the native language.
Requirements & Defects
A Requirement represents a singular
documented physical and functional need that
a particular product or process must be able
to perform.
A Defect represents a condition in a software
product which does not meet a software
requirement (as stated in the requirement
specifications) or end-user expectations
Xray Issuetypes
• Pre Condition-Initial conditions that must be
assured before the execution of a test
• Test – The steps that validate your Requirement ,
A test Case
• Test Set –A group of tests, organized in some
logical way
• Test Plan- A "formal" plan of the tests intended to be
executed for a given version.
• Test Execution-An assignable, "schedulable" task
to execute one or more tests for a given version
along with its results.
Process Flow
Specify
Organize
Plan
Execute
• Test
• Pre-Condition
Write Tests for the Requirement
• Test Set
• Test Repository
Organize In Test Sets/Repository
• Test Plan
Plan for a version in a Test Plan
• Test Execution
• Sub-Test Execution
Execute in one or more Test Executions
Project Structure
All in One
Arrangement
Project Structure
All in One
Arrangement
Project Structure
Process Flow
Epic
Story
• Specify the Feature
• Breakdown the
epics into Story’s
Defects
Test
Test Set
• Create Testcases
• Group the Testcases
into Test-Sets
Test Execution
Test Plan
• Execute the
testcase and mark
them Passed in Xray
• Plan the test cases
to be executed for
a given version
© 2018 MicroGenesis TechSoft Pvt Ltd. All Rights Reserved.
Writing & Specifying Test
• Test- A sequence of steps
coupled with conditions or
variables, test inputs and
an expected result.
Types of Tests :
• Manual- using Steps
• Cucumber- using Gherkin
• Generic- unstructured kind
Manual Test
Types of Testcase
• Manual
• Cucumber
• Generic
Action
Data
Expected
Result
Manual Test Step
• Import it from Json, Clipboard,
CSV
• Rearrange the Steps by dragdrop or simply adding the step
number
Cucumber Test
Types of Testcase
• Manual
• Cucumber – using
Gherkin
• Generic
Generic Test
Types of Testcase
• Manual
• Cucumber
• Generic
Pre-Conditions
Preconditions- specify the
conditions that need to be fulfilled
in order to execute a test.
Types of Testcase
• Manual
• Cucumber
• Generic
Pre-Conditions
• Associate Pre-Conditions with
Tests.
Types of Pre-condition
• Manual
• Cucumber
• Generic
Import Tests
TCID
1
Summary
Data
Result
Repository Path
/module A
/Calculator
Enter Value A
5
5
1
Enter Value B
10
10
1
Enter +
2
Test Addition
Step
Test Subtraction
15
Enter Value A
10
10
2
Enter Value B
5
5
2
Enter -
5
/module B
/Calculator
Test Coverage View
Test Coverage View
Test Coverage
Organizing Test
• Test Set – Collection of Tests
• Test Repository -enables the hierarchical organization of Tests at the project level by
allowing you to organize Tests in folders and sub-folders.
Organize using Testset
• Test Set – Collection of Tests
• Test can belong to multiple
Test sets.
• Adding Test-Set ,auto adds all
the related Tests.
Organize using Repository
Planning Test
➢ Which requirements you want to validate?
➢ How would you validate them?
➢ Will it manual or automated?
➢ Who and when will the test be executed?
Test Plan to give better
visibility over the tests to
be executed.
Test Plan Board
➢ Add Tests to the Test Plan
➢ Prioritize the Tests
➢ Create Test Executions for
the Associated Tests.
Test Plan Board
➢ Add Tests to the Test Plan
➢ Prioritize the Tests
➢ Create Test Executions for
the Associated Tests.
➢ Test Plan Boards to displays
the overall Execution Status
Test Execution
Test Execution - to monitors and
verifies if the Tests are working as
expected in a target context and
environment.
Overall Test Execution
Execute Test
Subtest Execution
• A Sub-Test Execution functions exactly
the same way as the Test
Execution issue type.
• The difference between them is that
the Sub-Test Execution is a subtask and can be created within the
context of a requirement.
• Creating a Test Execution as a subtask of the requirement issue provides
you the ability to track executions in
the Agile board.
Subtest Execution
• Do I have to use Subtest Executions?
• No, you don't. They're optional. If you don't want to use them, you can just remove the
issue type from your project.
• Why should I use Sub-Test Executions?
• They are handled as sub-tasks of the parent requirement. This means that you gain
some out-of-the-box features such as the:
•ability to track the progress of the Test Execution in the Agile board, by seeing it incontext with the parent requirement
•ability to count the time estimates of the Sub-Test Executions within the overall time
estimate at the parent requirement
•ability to optionally restrict workflow transition on the parent requirement based on the
workflow status of the related sub-tasks (e.g., allow transition of the requirement to
"closed" only if the Sub-Test Executions are also "closed"
Advantages of using JIRA Types
oOrganize the Data
oREST API to integrate with your testing tool
oWorkflows to Approve / Reject the Test
oAssignment & Accountability
oXray Work Logs
oSearch + JQL
oNotifications
oCSV Import
oReports & Dashboards
Reports & Analysis
➢ using standard JQL queries (Server)
➢ using the specific panels of Tests/Test Sets/Test Plans/Test
Executions
➢ using the Built-in Reports
➢ building dashboards using gadgets
In-built Project Reports
oTraceability Report
oOverall Requirement Coverage
oHistorical Requirement Coverage Report
oTest Plan Report
oTest Execution Report
oTest Run Reports
Traceability Report
➢ Shows the requirements
traceability through tests,
test runs and defects.
Test Execution Report
➢ Shows a list of Test Executions with metrics related to each execution
Test Coverage Report
➢ Calculates the test coverage
status for a list of coverable
issues for the selected
version or Test Plan, and/or
Test Environment. The
statuses are presented in a
normalized horizontal stacked
bar chart and evaluates the
completeness of each issue.
Gadget Reports
Gadget Reports
Gadget Reports
Enable Xray
• Enable Project structure , by adding the relevant Types.
Configure Requirements & Defects
• Define which issue type will be considered as Requirement.
Defect Mapping
• Define which issue type will be considered as Defects.
Miscellaneous Configurations
Thanks!