Even if we take it at face value that Jira was never built with test management functionality in mind, we're still in a world where QA teams and developers have to be in the same place.
Sometimes we just have to play the hand we're dealt.
When using Jira in your testing process, there are some things you can do to improve your experience.
Why "vanilla" Jira is not enough for your testing process?
At its core, Jira follows a very simple but effective logic – tasks must be closed. Sure, they can go through tons of stages, but in the end they're always pushed to "finish".
The same cannot be said for test cases. Sooner rather than later, you'll need to re-run or reuse your tests.
What are your options?
- Leave the "test case" issues open: this is one of those simple solutions that sound good but don't work. The practice of keeping cases open goes against Jira's nature: you'll just get lost with too many issues to track.
- Edit User Story to override test case: This method is to have User Story as test case andsubtasksin individual tests. This solution delays the side effects of keeping cases open, but does not eliminate them. Reusing tests will still be a pain.
- Add a new test case status to your workflow: this workaround is really smart. Marking something as "testing" or "QA" will prevent the tests from being moved to the "done" column, but at this point you're just following the next steps to be done.
- Take advantage of Jira QA tools from the Atlassian Marketplace: can't turn Jira into a QA tool? Take advantage of integrating a tool you already use, or add missing pieces of functionality with a handy add-on. For example, you can useSmart checklists template functionalityto create the steps necessary to run a test case once and they will be automatically available when you open a case of a certain type.
What distinguishes a good case management tool in Jira?
The Atlassian Marketplace is filled with hundreds of add-ons to suit every project management niche.
Heck, you'll get 286 results for the term "testing".
Certainly not all of these products are created equal. Even the better ones may not meet the needs of different QA teams that run different processes and rely on a multitude of test applications.
So what to look for in a Jira manual test or test automation tool?
- Learning curve:There is probably already an integration of the tools you are used to in the Atlassian Marketplace. In this case - you should go to them, because you already know the secrets of the solution. If you decide to go for something new, take a look at screenshots and interface reviews to make sense. The last thing you want to do is invest dozens of hours learning a new Jira add-on (unless there is a specific need). Also, keep in mind that in both cases you will at least have to learn something, so I suggest doing this in the earlier stages of implementing new software.
- Functionality:When it comes to bug tracking, you need to keep an eye on more than simple functions.
- Can an add-on solve your problem?specificrequirements?
- How will it handle scaling?
- Can it track the metrics you deem necessary or provide the data you need to create valuable reports?
- Integrations:Does the add-on fit with the processes your company already uses? I'm talking about having fun with the tools you use outside of Jira, such as the software you use to create a test plan or document results.
Free test management tools for Jira
What are the better Jira QA add-ons?
TestRail integration for Jira
This add-on integratesTestRail test management softwarein yoursWait for an example. It allows you to synchronize requirements between Jira and TestRail in real time, create test plans, run tests and analyze data from reports.
TestRail can be integrated with Jira Cloud, Jira Server and Jira Data Center. This integration provides full two-way synchronization of issues, bugs, and requirements.
Plus qualityis a powerful test management tool that provides transparent insight into test performance as well as previous test executions. The tool has a nice clean user interface. You can view bugs, links and reports almost effortlessly.
The downside is that you have to learn as you need to master the Jira functionality and learn a bit of JQL to be able to 100% use the add-on functionality. Also, there are only cloud and server versions of the add-on. Not available in Jira Data Center.
You've probably heardTeam Zephyrright now due to its popularity among Agile teams. Still, I think this add-on is worth mentioning as it has earned its spot on everyone's radar.
The lion's share of the add-on's popularity is due to how well it fits into agile development processes, thanks to its BDD integration, test automation and reporting solutions.
ZephyrSquad is available on Jira Cloud, Jira Server, and Jira DC.
QMeters for Jira
QMetry test management for Jirais a test management tool that allows for better involvement of quality control throughout the software life cycle. From a purely QA perspective, modular test scenarios can be created and reused, but there are even more options when it comes to collaborating on scenarios via HipChat, Jira Capture, and Confluence integrations.
QMetry for Jira is available in the cloud, server and data center.
TestRayit's a nice addition if you're looking for more traceability throughout the testing process. Test cases are conveniently organized as a tree, and integrations with Jenkins and Bamboo allow for better automated testing.
TestRay is available for Jira Cloud, Jira Server, and Jira Data Center.
How do Jira test management tools compare to each other?
|Name||Overview of the most important events||Review the result||Cena||Free trial|
|TestRail||Flexible test plan features|
Infrastructure designed to handle tens of thousands of tests
Configurable test automation API
|PLUS QUALITY||Access and create tests based on Jira issues|
Traceability reports that summarize errors related to test cases and their reports
The ability to add multiple tests to a test cycle through JQLTest definitions are introduced into tasks
|4||Free for up to 10 users / $1.50 per user per month||So|
|Team Zephyr||Integration with Cucumber for Jira|
Test results are synchronized via SmartBear
Real-time results and comprehensive traceability
Test automation and integration of BDD software
|3||$1 per user per month for up to 10 users. $4.55 for each user over 10 years old, but the price gets cheaper as you scale.||So|
|QMeters for Jira||Traceable by creating tests|
Audit historyIntegration with Cucumber, JUnit, TestNG, UFT
Free QMetry Open API for DevOps/CI test management. Automatic suggestion based on history details
|4||It starts at $1 per user per year and scales with the number of users||So|
|TestRay||Tracking from start to finish|
Requirements versioning and database management
Requirements traceability matrix JQL search for synapseRT data Bamboo and Jenkins integrations
Estimating and forecasting time
|3.5||Starting at $1,375 per 50 users per year.||So|
I don't want to sound cheesy, but teamwork really does make dreams come true. Developers and QA engineers must follow thembest practices in Jiraand efficient communication within a single project management software ecosystem. And while Jira isn't the perfect test management tool by default, you'll always find options in the Atlassian Marketplace that will make everyone's life a little better.
Everything is easier when the process is well documented and progress is visible at a glance.
Posted byOleksandr Siryi
Hi! My name is Oleksandr and I am an Atlassian Marketplace partner and a technical writer at Railsware. Most often I write about Jira, workflows, automation and project management, with particular emphasis on Agile practices.See all posts from Oleksandra Siryi