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

Ad hoc test run reports


Ad hoc test run reports indicate the number of times a selected test case has been executed as a part of an ad hoc test run. In this case, the test case is not a part of any test plan and is executed independently. It's also useful to track its status changes. If any artifacts are attached during the ad hoc test run, such as test data, screenshots, or logs, testers can use this information to compare the results from its last execution. Jira plugins have the option to generate such reports. Let's create them one by one.

synapseRT

synapseRT has the option to view the ad hoc test run details at an individual test case level from the Ad hoc Test Run section. As shown in the following screenshot, the selected test case has been executed three times and its status varies from BLOCKED to FAILED and PASSED. It also shows details such as the ID of the test run, who it was executed by, the execution date and time, and relevant defects, if any:

Ad hoc test run reports can be generated...