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

Creating the Jira issue type as requirement


In Jira, we have default issue types, such as Epic, Story, Task, Sub-task, and Bug. These issue types give us flexibility to define our own issue types as per the project's requirements. However, each of these issue types can be treated as a requirement. Once the requirements are defined and logged in the system, it becomes easy to track and manage them. We learned how to define requirements in Chapter 3, Understanding Components of Testing with Jira. So now, let's create them in Jira.

Creating requirements

Jira has a predefined set of fields to create Jira tickets. Additionally, we can add customized fields as required according to the selected issue type. Any requirement issue type should generally contain the following:

  • The purpose of the requirement or the task that the team is expected to accomplish
  • The detailed description that breaks the complex requirement down into further details and specifications
  • The issue type's priority
  • The issue type's...