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
3rd
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2025, in the Test Management Tools category, the mindshare of Adaptavist Test Management for Jira is 2.8%, down from 3.4% compared to the previous year. The mindshare of Tricentis qTest is 14.6%, up from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Market Share Distribution
ProductMarket Share (%)
Tricentis qTest14.6%
Adaptavist Test Management for Jira2.8%
Other82.6%
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.
SamuLehikoinen - PeerSpot reviewer
Efficient and collaborative software testing providing comprehensive test management capabilities, seamless integration with various tools and impressive manual regression testing features
The user interface has a somewhat outdated design, which is certainly an area that could be improved. Some of the modules appear to be loosely connected, but despite these aspects, our overall experience with the tool was positive. When you begin integrating your testing tools with qTest, the available examples may not be very clear, and I believe this is an area that could be enhanced, particularly in terms of providing clearer integration guidance. While the tool's integration with various testing tools is impressive, there is room for improvement in showcasing more cases and benefits, especially through additional videos and documentation.

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."
"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."
"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."
"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 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."
"The initial setup was very easy."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"The solution's real-time integration with JIRA is seamless."
"The JIRA integration is really important to us because it allows our business analysts to see test results inside the JIRA ticket and that we have met the definition of "done," and have made sure we tested to the requirements of the story."
"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."
 

Cons

"Lacking visual gadgets that go on a dashboard, pie charts, bar charts and histograms."
"They should work on integrating the solution with AI."
"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."
"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."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"As an admin, I'm unable to delete users. I'm only able to make a user inactive. This is a scenario about which I've already made a suggestion to qTest. When people leave the company, I should be able to delete them from qTest. I shouldn't have to have so many users."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"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."
"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."
 

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 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."
"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."
"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."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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 a little over $1,000 for a concurrent license."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
866,561 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
35%
Computer Software Company
30%
Manufacturing Company
11%
Performing Arts
4%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
11%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise13
 

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?
The solution is expensive. For the features that are available, depending on the volumes of licenses we get, we are able to get better discounts as strategic partners of Tosca. We can pass some ben...
What needs improvement with Tricentis qTest?
Customers are moving towards Tricentis due to their association with SAP. There is interest in understanding if there are connectors for converting UFT scripts to Tosca, as many customers are looki...
 

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: July 2025.
866,561 professionals have used our research since 2012.