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 new defects


Simply speaking, deviations from the anticipated results are regarded as defects. There are a few more terms that are used in the industry interchangeably to define a problem, such as a failure, bug, or error. However, any form of issue, no matter what it's called, must be resolved before launching the product.

Software defects can be the result of the following:

  • A feature is built based on invalid or incomplete requirements
  • A feature is stated in the requirements but the required software for it is missing
  • The function used in the code is not returning the expected results, or running in an infinite loop, or accepting an invalid number/type of an input parameter
  • Users are not restricted from performing invalid/unauthorized actions
  • Error messages as not shown as expected
  • Stated and unstated requirements are not met
  • Text and images are unreadable
  • Invalid code is merged into the build and is deployed in the test environment

Once there is confirmation that the behavior exhibited...