Try our new research platform with insights from 80,000+ expert users

Adaptavist Test Management for Jira vs Tricentis qTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Adaptavist Test Management ...
Ranking in Test Management Tools
10th
Average Rating
7.2
Reviews Sentiment
6.8
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Test Management Tools category, the mindshare of Adaptavist Test Management for Jira is 2.7%, down from 3.4% compared to the previous year. The mindshare of Tricentis qTest is 16.1%, up from 10.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

RS
Has dashboard and reporting features that help us identify and address red flags
I would like to see some improvements in Adaptive Test Management for Jira. First, having a recommendation engine or feature that guides handling risks more intuitively rather than relying on manual processes would be helpful. Second, enhancing the connectivity with third-party tools like Teams or Slack would be valuable. One challenge with integrating Adaptavist Test Management for Jira into workflows is ensuring it accurately tags and incorporates all relevant stories and epics. Sometimes, it’s unclear if the tool considers all dependencies and backlog items, which can affect how risks are assessed. However, it sometimes seems to miss this high-level perspective, which can be a limitation based on how the product is designed. This has been a concern for those who use it regularly, although I don’t manage these aspects personally.
Sudipto Dey - PeerSpot reviewer
It doesn't require installation because you can use it through the URL; it's user-friendly and has an excellent reporting feature
The support for Tricentis qTest has room for improvement. The response could be better. There's a feature I want to document on the Tricentis Idea Portal for Tricentis qTest, which I hope to see in the next version of the tool. It's a feature available in Micro Focus where you execute a test, and then on a spec level, you mark it as pass or fail. Then at the overall level, Micro Focus will automatically mark the test as a pass if all steps passed or failed, even if one step failed. However, here in Tricentis qTest, you still need to mark the overall level of the test cases. It's not automated, unlike what you have in Micro Focus. If Tricentis adds that feature in Tricentis qTest, it will make life easier for testers.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We don't use technical support. We have an office in Austria that provides us with solutions. Also, this solution is pretty simple and user-friendly. We don't really need help with it."
"Our software development process primarily uses Adaptive Test Management for Jira to monitor real-time risks across all stories and sprint planning. Additionally, we use it to create action plans for high-priority risks."
"You can group test cases together and track the execution of them."
"The program is very stable and scalable."
"It is a scalable solution."
"Being able to log into Defects, go right into JIRA, add that defect to the user story, right there at that point, means we connect all of that. That is functionality we haven't had in the past. As a communication hub, it works really well. It's pretty much a closed loop; it's all contained right there. There's no delay. You're getting from the defect to the system to JIRA to the developer."
"The most important feature which I like in qTest manager is the user-friendliness, especially the tabs. Since I'm the admin, I use the configuration field settings and allocate the use cases to the different QA people. It is not difficult, as a QA person, for me to understand what is happening behind the scenes."
"qTest helps us compile issues and have one place to look for them. We're not chasing down emails and other sources. So in the grand scheme of things, it does help to resolve issues faster because everyone is working off of the same information in one location."
"I like the way it structures a project... We're able to put the test cases into qTest or modify something that's already there, so it's a reusable-type of environment. It is very important that we can do that and change our test data as needed..."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"The solution's real-time integration with JIRA is seamless."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"The initial setup was very easy."
 

Cons

"I don't like that you need to use a lot of tabs. One test case takes 15-20 minutes and on Zephyr is take about 5-10 minutes."
"They should work on integrating the solution with AI."
"Lacking visual gadgets that go on a dashboard, pie charts, bar charts and histograms."
"I would like to see some improvements in Adaptive Test Management for Jira. First, having a recommendation engine or feature that guides handling risks more intuitively rather than relying on manual processes would be helpful. Second, enhancing the connectivity with third-party tools like Teams or Slack would be valuable."
"The Insights reporting engine has a good test-metrics tracking dashboard. The overall intent is good... But the execution is a little bit limited... the results are not consistent. The basic premise and functionality work fine... It is a little clunky with some of the advanced metrics. Some of the colorings are a little unique."
"The support for Tricentis qTest has room for improvement. The response could be better."
"We faced challenges when trying to consolidate data in a repository, and similar features were lacking in qTest. It also does not allow for task tracking or calculating time spent on tasks, which affects project timelines."
"I really can't stand the Defects module. It's not easy to use. ALM's... Defects Module is really robust. You can actually walk through each defect by just clicking an arrow... But with the qTest Defects module you can't do that. You have to run a query. You're pretty much just querying a database. It's not really a module, or at least a robust module. Everything is very manual."
"We feel the integration between JIRA and qTest could be done even better. It's not as user-friendly as qTest's other features. The JIRA integration with qTest needs to mature a lot... We need smarter execution with JIRA in the case of failures, so that the way we pull out the issues again for the next round is easy... Locating JIRA defects corresponding to a trait from the test results is something of a challenge."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"Reporting shouldn't be so difficult. I shouldn't have to write so many queries to get the data I'm looking for, for a set of metrics about how many releases we had. I still have to break those spreadsheets out of there to get the data I need."
"The installation of the software could be streamlined. We pay for the on-premise support and they help us a lot, but the installation is something which is very command-line oriented."
 

Pricing and Cost Advice

"The tool's pricing is a bit expensive, considering the kind of risk analysis and visibility we want, given that it's built on top of the Jira platform and other Atlassian products. It's priced slightly higher than similar products, maybe five to ten percent more."
"The licensing is rather expensive for those that have many users."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"We're paying a little over $1,000 for a concurrent license."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"It's quite a few times more costly than other tools on the market."
"For me, pricing for Tricentis qTest is moderate, so that's a five out of ten. It's more affordable than my company's previous solution, which was Micro Focus ALM."
"Our license price point is somewhere between $1,000 and $2,000 a year."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
38%
Computer Software Company
26%
Manufacturing Company
9%
Insurance Company
6%
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
11%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Adaptavist Test Management for Jira?
The tool's pricing is a bit expensive, considering the kind of risk analysis and visibility we want, given that it's built on top of the Jira platform and other Atlassian products. It's priced slig...
What needs improvement with Adaptavist Test Management for Jira?
I would like to see some improvements in Adaptive Test Management for Jira. First, having a recommendation engine or feature that guides handling risks more intuitively rather than relying on manua...
What do you like most about Tricentis qTest?
I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests.
What is your experience regarding pricing and costs for Tricentis qTest?
Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray.
What needs improvement with Tricentis qTest?
Tricentis qTest needs improvement in its repositories' functionality. Unlike Azure, it does not have repositories to upload scripts. Additionally, it lacks features like task addition and tracking ...
 

Also Known As

No data available
qTest
 

Overview

 

Sample Customers

IBM, John Lewis, Trip Advisor, Netgear,  Bill and Melinda Gates foundation, Sapient
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about Adaptavist Test Management for Jira vs. Tricentis qTest and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.