Afsana Atar - Hands-On Test Management with Jira: End-to-end test management with Zephyr, synapseRT, and Jenkins in Jira

Test Management has a folder structure for organizing test cases, hence when generating a report based on a test suite, we will have to select the option based on the folder:

1. In order to generate the test suite report in Test Management, navigate to the Tests | Reports | Test Execution tab and enter the required details. As shown in the following screenshot, enter the project name, the Folder (test suite) for which a report needs to be generated, and so on, and click on the Generate button:

1. This generates the report shown in the following screenshot. It lists details such as the folder name for which this report has been created, the total number of test cases, and their execution statuses. It also indicates the percentage of the test cases in any given status. In this case, we have 33.33% of test cases in the Pass status. It also shows details regarding how much of the test execution is remaining, has been Completed , and so on. The Issues section lists defects linked to the test cases, if any:

Lets start by creating a Scrum project in J ira :

1. Once you select the Scrum software development option, it takes you to the following page. The listed Issue Types will be available as default Issue Types for your project with the specified default workflow . Remember, you can always add new or modify existing issue types and workflows. This is shown in the following screenshot:

1. Provide a Name for your project with a Key and assign the Project Lead , as shown in the following screenshot:

1. On clicking Submit , the project will be created, and you will see the project Backlog page, as shown in the following screenshot:

1. Now, you are ready to add project backlog items by creating issues and plans, and organize them by creating sprints and starting iterations. The following screenshot shows a sample active Scrum project for Sample Sprint 2 :

In this chapter, we learned about the DevOps pipeline and execution using Jira plugins. We learned how the DevOps pipeline can be leveraged in a software development project to become truly agile and deliver continuously, while improving in making deliveries. We configured our Test Management plugins for Jira to integrate with Jenkins as our CI/CD tool. We saw a simple hands-on example of working in the DevOps pipeline for automating test case management.

Here comes the end of our long journey. I hope you enjoyed reading this book!

Software products can only be trusted if they generate satisfactory results without any faults. Invalid results can have a negative impact on end users. Faulty products can make consumers unhappy and cause frustration. Hence, identifying faults or problems in time can aid developers in delivering a good quality product. However, we need to understand how to classify defects, along with an effective way of reporting them, so as to confirm whether the defect has been resolved.

In this chapter, we will cover the following topics:

• Understanding the importance of logging defects
• Creating new defects
• Linking existing defects to test cases

We will also see how Jira helps us in tracking and managing defects effectively.

Zephyr also identifies a test case as another issue type. To create a test case in Zephyr, we need to follow these steps:

1. Select the issue type as Test . We also need to enter the other required details such as Summary , Description , Priority , Linked Issues , Assignee , Test Step with Expected Result , and Test Data . Click on the Create button to create the test case:

1. After creating the test case, you will see that it has all the details that we have entered. Like any Jira ticket, we can always modify these details. We also have the option to Clone the test case, add more related issues or requirements, or even start executing by clicking the Execute button:

Managing test artifacts involves storing and managing the evidence that has been generated as a part of the test execution phase, or it can also be a set of deliverables generated after any phase of the SDLC.

These artifacts are very useful when managed properly:

• Artifacts generated during defect logging and retesting saves time for both developers and testers, preventing them from having to debug every part of the code, reproducing tests using specified test data, a build version and environment. Log error files, screenshots, database queries with the result set, input parameters, the URL of the application used during testing, the environment, the date tested on, the build number, and so on.
• Deliverables generated after the execution of each phase in the SDLC, such as project charters, BRDs, test plans, RTMs, and test execution reports, often serve as input to the subsequent phase and help teams to focus on the objective and track the progress of a project.
• Other types of artifacts, such as code review or inspection reports, project performance reports, and lessons learned reports, can be useful across the organization and can be used by other team members to make changes to their current strategy. These documents can be part of knowledge base of an organization.
• Training documents, templates (for project management plans, project charters, or requirement specifications) are also part of knowledge management and serve the training needs of new recruits to know more about the organization, its products, and standards followed by them.
• The end user's manual or product-specification documents are usually shared with end users, by the organization, to help them use software or services effectively.