At STH, we are all about sharing the best practices, tools, techniques, processes, tips and everything else that we have enjoyed learning and benefited from using. We believe this makes day to day tasks easier and helps us all grow as testers.
Today is one such attempt – the integration of JIRA with qTest to gain the benefits of test management linked to requirements management.
What You Will Learn:
JIRA is a leading issue and project tracking tool catering to agile QA and development teams. JIRA allows you to manage and track any kind of unit work in the form of “issues” bugs, stories, project tasks with a predefined workflow.
Also read => Complete JIRA tutorials
qTest by QASymphony is a test management solution that allows teams of all sizes the ability to easily, manage, organize and report on software testing and test case management efforts.
Also read => Hands-on qTest review
When you pair JIRA’s best-of-breed issue and project tracking capabilities with qTest’s innovative test case management abilities, the result will change the way your development and testing teams work.
Here are just a few of the benefits for integrating JIRA and qTest:
Check out this JIRA test management integration video for all you need to know about this. The integration is seamless and super easy to setup.
OK, the tools are connected. Now, what?
Let’s start working through the steps of the resulting integrated requirement-test-defect management solution.
First of all, notice how the interface changes. You will no longer see the “defects” tab. This is because all defects raised through qTest will be created in JIRA as issue type “BUG”.
(Note: click on any image for enlarged view)
Check this- no defects tab.
Step #1: Retrieve requirements.
Requirements are always managed in a centralized way from JIRA. That part stays as is. But test management should start from requirements too, shouldn’t it? So, instead of having to create a brand new instance, the integration provides a way in which a certain issue type from JIRA can be retrieved into qTest.
Usually, the requirements are of the issue type- “New feature”, “Improvement” or “Story”.
Once requirements are downloaded, they would appear as:
Note that, the icons are different. The JIRA and qTest ID’s both exist; JIRA and qTest properties too. These requirements are read-only here. They can be linked to TCs that exist within JIRA. Any changes to these requirements in JIRA are reflected on refresh.
Step #2: Create test cases and link them to requirements
This process is the same with or without JIRA integration. The test cases once linked to a requirement (retrieved from JIRA) will result in a JIRA issue link so the developers can see the test/tests associated with it.
This not only improves awareness of what the cross-functional teams are up to, but also supports test-driven development.
Check out the link as it appears in JIRA:
Step #3: Create test cycles and run
This step too does not change at all with the integration. Test teams would go ahead and create Test cycles and/or Test suites within qTest and carry out test execution.
If a certain Test run results in a failure or if a defect reported is linked to a Test run, then this relationship reflects in JIRA. Two things happen here:
Number one: The defect gets linked to the requirement (if the test case was linked to a retrieved JIRA requirement).
Number two: The defect will get a link to the Test run whose failure resulted in the issue.
Step #4: Report defects
When a test run or a test step failure results in a defect and a qTest user clicks on the “BUG icon-”, JIRA Create Issue page (with issue type: Bug, auto selected) opens up automatically. Enter the information and create the issue.
The links are created as described in the earlier step.
Step #5: Analytics and Reports
For a quick look up on the JIRA-qTest integration, JIRA users are provided with a qTest Widget. The following information is available on a real-time basis:
qTest reports are all available as usual and can be created around JIRA retrieved assets too.
#1) Testers can be testers and developers can be developers. I mean, test management systems are built for testers. Take a look at the qTest UI. The sequence of actions you would normally perform in a test project (STLC- Requirement gathering-Test design-Test execution-defects) is how the interface is organized. JIRA is more development centric, so you will not find this structure there.
#3) Any updates to the requirements are automatically refreshed into qTest. So there will never be a discord.
#4) Defects are centralized in JIRA. It does not mean qTest users have to log out of their qTest instance when they have to log a defect. When you choose the option to log a bug, qTest automatically invokes the JIRA instance and returns back to the qTest when the bug is submitted.
#5) Developers can see the “Test run” information linked to a defect, so if there are multiple runs or if the developer wants to know if the defect was retested as a latest test run or not, they can do that from the JIRA interface itself.
#6) Reports both at JIRA and qTest. Through the qTest Widget in JIRA, the analytics can be viewed that show the highlights of the integration. qTest reports, on the other hand, use the JIRA retrieved elements to provide test statistics.
As always, we hope you find this article interesting and useful.
Tool collaboration is a trend that QA and development teams are most thankful for (at least I hope they are) and integrations for JIRA test management, specifically qTest, is a definite benchmark.
About the author: This how-to guide is written by STM team member Swati S.
Do give it a try and let us know if this worked for your team! Your feedback, comments and questions are most welcome!