Atlassian Jira is one of the most popular project management software. Besides the core features the software offers, it has an extensive marketplace of plug-ins to support various phases of software development processes.
While there are several test management plug-ins that can be integrated with Jira, yet many of us often wonder how to select the appropriate one for their project needs. The selection of these plug-ins depends on the project requirements, pricing, test traceability to its features/stories and bugs, reports, project development model, etc. In this article, we will be focusing on some of these plug-ins that are available for test management and share a few quick insights on selecting the appropriate plug-ins.
After reading this article, you should have sufficient information on selecting the right test management approach that suits your requirements, using the right test management tool.
Test Case Management Plug-ins for Jira
Among several test management plug-ins available for Jira in the Atlassian marketplace, the following are some of the popular ones by their usage statistics –
- Test Rail
Here is a comparison matrix that has been drafted based on the used features, pricing, number of installations, etc.
Apart from the above list of features, all the upcoming features, existing issues, and related documentation can be found in the respective sites (link provided)
- Zephyr – Reviews, Roadmap, Documentation & Pricing Cloud
- TM4J – Reviews, Roadmap, Documentation & Pricing Cloud
- XRAY – Reviews, Roadmap, Documentation & Pricing Cloud
- Test Rail – Reviews, Roadmap, Documentation & Pricing Cloud
- RTM – Reviews, Roadmap, Documentation & Pricing Cloud
All these plug-ins support basic test management features such as test case creation, test cycle creation, test executions, results tracking, and report generation.
Based on the features, tool experiences, and user reviews, we have listed down tool wise Pros and Cons.
Pros: Enables planning Adhoc or structured test execution cycles. It has a simple and easy application UI and can integrate with all leading automation tools such as SoapUI Pro, Test Complete, Cross Browser Testing, Load Ninja, and Cucumber.
Cons: Importing of test cases requires another plugin (zfj-importer). It has a comparatively high price and cannot customize the test case format.
Pros: It can be used for manual and automation projects and allows the reuse of test cases across all projects. It eliminates duplicate test cases and allows better organizing of folders/libraries.
Cons: Relations between testing objects (such as test case, test plan, defects, coverage) is only possible via web links even though it has traceability, but all are displayed as a separate list. The filter options are minimal, which makes tracking/generating reports a little complex.
Pros: It provides customizable screens and workflows, test automation support, versioning, or gives test case history.
Cons: The tool has low performance when used at large scale, with complex reporting structure, and does not give a clear view of process/executions.
Pros: A very comprehensive API that can be used to integrate with various tools, frameworks, and third-party applications. It also provides the ability to customize the user interface.
Cons: It can be confusing with traceability of test cases and does not recover deleted cases.
Pros: The tool provides plug and play features, imports test cases from external tools in a hassle-free migration, and can generate requirement coverage report.
Cons: It does not provide any support for automation tools integration and complex cross-project workflows.
While we are now aware of the most used Jira plug-ins, we also know the pros and cons of the plug-ins. By focusing on the specific requirements and choosing the right plug-in, one can easily leverage Jira to accelerate and create a hassle-free testing environment. To know more about our testing methodology and for further information, visit our company website and contact us.
Please note that the above analysis is purely based on our collective personal experience and that readers are encouraged to carry out their due diligence before selecting the right plugin/tool to meet their needs. Also, we do not have any affiliations with the plugin development companies referred to in this article.
By: Srikanth Nagavarapu and Eeswar Pagadala