Book Image

Hands-On Test Management with Jira

By : Afsana Atar
Book Image

Hands-On Test Management with Jira

By: Afsana Atar

Overview of this book

Hands-On Test Management with Jira begins by introducing you to the basic concepts of Jira and takes you through real-world software testing processes followed by various organizations. As you progress through the chapters, the book explores and compares the three most popular Jira plugins—Zephyr, Test Management, and synapseRT. With this book, you’ll gain a practical understanding of test management processes using Jira. You’ll learn how to create and manage projects, create Jira tickets to manage customer requirements, and track Jira tickets. You’ll also understand how to develop test plans, test cases, and test suites, and create defects and requirement traceability matrices, as well as generating reports in Jira. Toward the end, you’ll understand how Jira can help the SQA teams to use the DevOps pipeline for automating execution and managing test cases. You’ll get to grips with configuring Jira with Jenkins to execute automated test cases in Selenium. By the end of this book, you’ll have gained a clear understanding of how to model and implement test management processes using Jira.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Linking existing defects to test cases


Establishing a relationship between defects and test cases helps to identify the impact of a defect on the current execution of test cases. If a single defect impacts more than one test case, then the testers can link the same defect to all the impacted test cases and update the test case status as Blocked.

However, apart from the impact analysis, it also helps in generating the traceability matrix where the requirements are linked to the test cases and test cases are linked to the defect. Defects can be linked to the test case at the test case level or test step level. If a test case has a greater number of test steps, and there are multiple defects observed for the same test cases, then in such cases, it makes more sense to link these defects at the test step level to identify at which step specifically the error has occurred.

Changing a test case status with regard to defects

Whenever the test team logs a defect and links it to the relevant test case...