The testing process iscomposed of multiple stagesand involves work of every team member, including analysts, testers, and developers. No matter how many people participate in the project and tasks, management of such a process requires a well-organized environmentthat allows tracking every step of the way from end to end.As we learned previously,Jiraseems to be the perfect choice for the job being a tool created for teamwork coordination, especially in software development.Imagine how much easier your team members’ life would be if all actions from collecting the requirements to reporting the defects were tracked in one place! While Jira is considered by many only as a project management tool, there are Marketplace apps tightly integrated with it and designed to make the testing journey more effective.One of them is ourRequirements and Test Management for Jira Cloud (RTM).
Why choose RTM as a plugin for testing in Jira
If you’ve decided on bringingyour testing inside Jira, congratulations! There area lot of benefits of doing so, andRequirements and Test Management for Jirais here to help you discover them all.First of all,our app’s interface is designed exclusively for Jira Software. That means you and your teamcan work with analreadyknown solution, which doesn’t require any special training,and it takes only3 stepsto configure the app:
- adding RTM issue types to the project;
- adding fields to the screens;
- grantingpermissionsto the testing team.
Thenwe can start our testing adventure right away!
RTMprovidesa hierarchical organization of all objectsin folders and subfolders andmakes gathering requirementsas essential as setting up test cases.Another key point is that the appallows you to seamlessly link requirements,testcases, and defectstoEpics and user stories,as well as search for them like for regular Jira issues.This level of integration gives you and your team the possibility of tracking the whole software project inside your Atlassian suite.
Setting up Requirements and TestManagement for Jirain 6 steps
1.Gather requirements in Jira
In theRequirementsmodule,on theDetailstab, we define the type of Requirements. You can choose amongUI Requirement,Functional Requirement,Non-Functional Requirement,andBusinessRequirementissue types.The next step is adding aSummarydefining what your requirement is about. Further custom fields aren’t obligatory but remember:the more details weadd,the clearer our intentions will be for the other team members.That’s why it’s a good idea to include a short description and all basicinformationlikeAssignee,Components,andLabels.It’s important to fill theAssigneefieldbecause it determines theperson responsiblefor the particular requirement.Usually, it’s theProduct Owner, but depending on a project or a product, it could also be the Test Analyst or the TestManager.
Just like all app objects, requirements inRTMare displayedin a transparent tree-view structure.In order to manage them, we click the folder icon and create folders and subfolders as we see fit. Elements on the tree view provide a possibility of drag and dropping and customizing. That kind of transparency will surely help organize the product development process from the very beginning.
2.Link tests to requirements in Jira
When requirements are in order,the next step is tocreate test cases. It can be done directly from theTest Casestab on a requirementview,or in theTest Casesmodule. The creationscreen on theDetailstablooks very similar to the previous one, except there are more fields to fill in. Here we can defineRTM Environment(like Android or iOS),Fix version/s,andEstimated Time.
Then we createStepsfor theTest CasewithPreconditionsandActionsto take.TheStepspanelisfully customizable:we can rename and define columns as well as their size, drag and drop elementsand combine theStepsinto groups.It’s equally important to write inInputsandExpected results.If it suits your team better, it’salso possible toimport data from aCSV file.That functionality helps to save time spent on retyping steps from Excel spreadsheets.
On theRelationstab, we’ll find the details concerning all the connections between objects:which requirements are covered by related test casesandwhich Jira Epics and/or user stories contain the features that require testing.
3.Check Tests Traceabilityin Jira
TheTraceability Matrixshows all types of relations on a special screen. Thanks to this functionality, verification of the whole structure of objects is far more efficient. It’s worth remembering thatwhat is shown on the X and Y axes is fully customizable with JQL so that we can choose which objects we’d like to display.RTM Traceability Matrixallows checking the coverage of Requirements by Test Cases, making sure that all Test Cases are included in Test Plans and Test Executions, verifying the Defects linked with Test Cases and Executions, and confirming that Test Plans are completed in Test Executions. Data from the Traceability Matrix panel can also be exported to a CSV file.
4. Design a test plan in Jira
After adding all the Requirements and Test Casesto the project, wecreate a Test Plan. On theDetailsandTest Casestabs, wedescribe ourTest Plananddecide which cases we would like to include in them. It’s worth mentioning that the Test Plans are reusable, so we can re-execute them or just particular Test Cases (that option automatically creates a new Test Plan for the selected ones). Each Test Case can also be executed as a Test Plan from theTest Casesmodule. What needs to be done is choosing one or severalTest Casesfrom the list and starting execution by clickingExecute as new TP.
5. Track test executions in Jira
TheTestExecutionsmodule is designed to follow the Test Plan progress. The multi-colored progress bar at the top of the screen shows the percentage of completed Test Cases and their statuses, whereas the table below presents detailedResultsof Test Cases,Assignees, Priority,and other information if any was set up manually before. The module also contains theTest Cases Executionscreen which we can see after choosing any Test Case from the list. This allows us to see the details of each Test Case’s realization and simplifies following which steps were passed, failed, or where there were difficulties.
RTMhas also dedicatedTest ExecutionandTest Case Executionreports, so you can verify theirprogress on a single screen or export data to a .csv file, if necessary. When creating the reports, you can filter the results byProject, Test Plan, Execution, RTM Environment, TCE Created Date,andTCE Assignee. BothTEandTCEare generated as a chart with the transparent table below, which makes it possible to check the details of each particular Test Execution or Test Case, depending on the report.
6. Report test results in Jira
If during the execution aTest Caseturns out to be failed,it requirescreating a Defect. To make the communication between developers and testers easier, we enabledaddingcomments andattachments to the appropriate Steps, like screenshots or log files. Like all the other objects inRTM, Defects can also be linked to other elements of the testing and development process so that it’s easier to track failures and find out why particular actions didn’t succeed.
TheRequirement Coveragereport makes it possible to confirm if our requirements are covered by Test Cases, Test Plans, Test Executions, Test Cases Executions, and linked to related Defects. Thanks to that, it will be easier for your team members to spot possible omissions and take care of them before the final product will be released.
The quality of software testing relies largely on a tool that we use.Requirements and Test Management for Jira appallows you and your team to seamlessly implement it into your software development process. Our app is fully integrated with Jira Software, which allows us to do the following:
- track both development and testing progress in a single place;
- organize objects in each module into a customizable tree-structured view;
- seamlessly link objects to each other and to Jira Issues as well;
- create reusable Test Plans;
- preventbugs on the “left side” of theproject.
You and your team might already be familiar with Jira as a project-tracking tool.The app’s well-known UI will help you quickly adjust to the look and feel and does not require any additional training for the team. Now you can focus on delivering the highest quality software.