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

Managing test artifacts and their formats


Test cases can be written and captured in a variety of formats, such as being stored in text files, Word documents, Excel workbooks, or by utilizing specialized test capture tools. The most prevalent way, however, is creating test cases in Excel sheets and loading them into the test management tools such as HP ALM, Jira and so on.

Apart from the detailed test execution steps, a test case can also have a variety of support documents or artifacts attached, such as the following:

  • A prototype document that testers want to refer to during the execution phase
  • User credentials
  • A set of SQL queries and/or procedures that are needed for test execution
  • Details regarding the scheduled jobs
  • Links to documents that can be referred to during execution

Additionally, if the same test case has been utilized for one or more releases, then it can contain the execution artifacts, such as log files or screenshots that were generated during the previous release test. It is quite...