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

"It is a scalable solution."
"The program is very stable and scalable."
"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."
"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."
"Works well for test management and is a good testing repository."
"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 main thing that really stuck out when we started using this tool, is the linkability of qTest to JIRA, and the traceability of tying JIRA requirement and defects directly with qTest. So when you're executing test cases, if you go to fail it, it automatically links and opens up a JIRA window. You're able to actually write up a ticket and it automatically ties it to the test case itself."
"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."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"What I found most valuable in Tricentis qTest is that it doesn't require installation. You use it through the URL. It also has an excellent reporting feature."
"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."
"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."
 

Cons

"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."
"Lacking visual gadgets that go on a dashboard, pie charts, bar charts and histograms."
"They should work on integrating the solution with AI."
"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."
"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 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 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."
"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 user interface has a somewhat outdated design, which is certainly an area that could be improved."
"I would really love to find a way to get the results, into qTest Manager, of Jenkins' executing my Selenium scripts, so that when I look at everything I can look at the whole rather than the parts. Right now, I can only see what happens manually. Automation-wise, we track it in bulk, as opposed to the discrete test cases that are performed. So that connection point would be really interesting for me."
"You can add what I believe are called suites and modules. I opened a ticket on this as to what's the difference. And it seems there's very little difference. In some places, the documentation says there's no difference. You just use them to organize how you want. But they're not quite the same because there are some options you can do under one and not the other. That gets confusing. But since they are very close to the same, people use them differently and that creates a lack of consistency."
"The support for Tricentis qTest has room for improvement. The response could be better."
 

Pricing and Cost Advice

"The licensing is rather expensive for those that have many users."
"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."
"We're paying a little over $1,000 for a concurrent license."
"It's quite a few times more costly than other tools on the market."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"We signed for a year and I believe we paid $24,000 for Flood, Manager, and the qTest Insights. We paid an extra for $4,000 for the migration support."
"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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
848,476 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
37%
Computer Software Company
27%
Manufacturing Company
9%
Insurance Company
6%
Financial Services Firm
13%
Manufacturing Company
12%
Computer Software Company
12%
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: April 2025.
848,476 professionals have used our research since 2012.