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
11th
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.2
Reviews Sentiment
6.1
Number of Reviews
19
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Test Management Tools category, the mindshare of Adaptavist Test Management for Jira is 2.5%, down from 2.6% compared to the previous year. The mindshare of Tricentis qTest is 8.7%, down from 15.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Market Share Distribution
ProductMarket Share (%)
Tricentis qTest8.7%
Adaptavist Test Management for Jira2.5%
Other88.8%
Test Management Tools
 

Featured Reviews

RS
Director of Product at Indian Institute of Management Bangalore
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.
reviewer2356440 - PeerSpot reviewer
Senior Director at a tech vendor with 10,001+ employees
User stories and test artifacts migrate seamlessly to innovative management tools
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 looking to make this transition. We have developed capabilities for automated migration from ALM to Tricentis qTest without any loss of data. However, for UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available. From a project perspective, there have not been many challenges with Tricentis products. The main improvement area would be developing a connector to move UFT scripts to Tosca, which would enable quicker and easier movement for customers. This would aid faster adoption of Tosca and ease the financial pressure on clients who currently need to invest in rewriting scripts.

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."
"You can group test cases together and track the execution of them."
"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."
"The test automation tracking is valuable because our automated testing systems are distributed and they did not necessarily have a single point where they would come together and be reported. Having all of them report back to qTest, and having one central place where all of my test executions are tracked and reported on, is incredibly valuable because it saves time."
"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 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..."
"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 self-healing aspects and maintenance of scripts are much faster and quicker, and we are able to find better avenues and better productivity in terms of maintenance, which we can pass on to the customer."
"Works well for test management and is a good testing repository."
"UI and UX are pretty easy to understand without much of a problem."
 

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."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"Could use additional integration so that there is a testing automation continuum."
"The support for Tricentis qTest has room for improvement. The response could be better."
"One of the things I noticed was the reporting part wasn't very good."
"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 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."
 

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."
"For the 35 concurrent licenses, we pay something like $35,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."
"It's quite a few times more costly than other tools on the market."
"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."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
34%
Computer Software Company
22%
Manufacturing Company
10%
Performing Arts
7%
Financial Services Firm
17%
Manufacturing Company
11%
Healthcare Company
10%
Insurance Company
9%
 

Company Size

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

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 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?
One of the things I noticed was the reporting part wasn't very good. It was hard to customize the dashboards in Tricentis qTest, and there were limitations in the dashboard. There may be missing fe...
What is your primary use case for Tricentis qTest?
The main use cases for Tricentis qTest are for test management, to keep test cases and execute those. Overall, centralized test management with Tricentis qTest was beneficial for the team's product...
 

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: December 2025.
881,082 professionals have used our research since 2012.