Book Overview & Buying
Table Of Contents
Feedback & Rating

Hands-On Test Management with Jira

By : Afsana Atar

5 (1)

Buy this Book

Hands-On Test Management with Jira

5 (1)

By: Afsana Atar

Buy this Book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Section 1: Introduction to Software Quality Assurance

An Overview of Software Quality Assurance

What is quality?

How do we ensure quality?

Software testing thought process

Quality Management Systems

Software Development Life Cycle versus Software Testing Life Cycle

Types of testing

Preparing test data and managing test artifacts

Summary

Section 2: Jira Environment - An Overview

Getting Started with Jira

What is Jira?

Organizing projects with Jira

Project initiation and management

Exploring test management plugins for Jira

Summary

Understanding Components of Testing with Jira

Requirements

Test suites

Test plans

Traceability

Reports

Summary

Section 3: Test Management - Manage and Plan

Test Management Approach

Execution strategy for structured testing with TMap

Best practices for test management

Summary

Test Planning

Creating and organizing a test plan using Jira plugins

Defining and implementing the test strategy

Establishing relations between requirements and the test plan

Summary

Section 4: Test Management - Design and Execute

Test Design Phase

Creating test cases

Managing test artifacts and their formats

Reusing test cases across different projects

Organizing test cases in main and subtest suites

Summary

Test Execution Phase

Defining test cycles

Adding test cases to the test cycle from the same project

Adding test cases to the test cycle from a different project

Summary

Defect Management Phase

Understanding the importance of logging defects

Creating new defects

Linking existing defects to test cases

Summary

Section 5: Test Management - Monitor and Control

Requirement Management

Creating the Jira issue type as requirement

Establishing relations between requirements and test cases

Summary

Test Execution Status Reporting

Test plan execution reports

Ad hoc test run reports

Requirement-based reports

Defect matrix reports

Test suite report

Burndown chart

Summary

Section 6: Continuous Integration with Jira and Jenkins

Jira Integration with Automated Testing Tools

Understanding the DevOps pipeline

Configuring Jira plugins to connect to Jenkins

Example workflow to integrate and execute automated scripts

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

5 (1)

5 star

100%

4 star

3 star

2 star

1 star

Reusing test cases across different projects

Now that we have learned how to write new test cases, let's look at how we can efficiently reuse existing ones for the project.

For a completely new project or release that doesn't have any dependent or related artifacts from past projects or releases, the test team must design all the test cases for all of the feature requests being released. However, as the product evolves and undergoes multiple releases, some of the common untouched features remain stable. This makes way for an opportunity to reuse test cases for future releases.

There are various reasons why you would want to reuse existing test cases:

If you have a new team member joining the team, the existing test cases can help them familiarize with the product by going through the existing test cases.
It reduces the overhead of creating all the test cases for...