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

Understanding the importance of logging defects


Before understanding the importance of defects, let's understand what a defect actually means in the software industry. When teams start working on a part or component of the project, they start building it with a predefined set of requirements or conditions. Similarly, when the test team creates test cases, they base them on the same set of requirements for the respective components.

Now, during the test execution phase, the test team starts validating the actual product in the test environment by interacting with the application step by step, since the end user will perform the same actions, and compare them with the expected results. If the result matches, testers can pass the selected step or test case. However, if the results are different, then we refer to it as a defect.

There are various reasons why the testing team would want to track the issues that occur during the development of the project. Some of the pros and cons are listed here...