No more typing reviews! Try our Samantha, our new voice AI agent.

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
12th
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
5th
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 May 2026, in the Test Management Tools category, the mindshare of Adaptavist Test Management for Jira is 2.0%, down from 2.8% compared to the previous year. The mindshare of Tricentis qTest is 6.2%, down from 16.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Mindshare Distribution
ProductMindshare (%)
Tricentis qTest6.2%
Adaptavist Test Management for Jira2.0%
Other91.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."
"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."
"Test Management for Jira provides a repository for our test cases."
"The program is very stable and scalable."
"You can group test cases together and track the execution of them."
"It is a scalable solution."
"The program is very stable, and that is why we have so much success with it."
"My impression of the stability is very positive."
"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."
"Overall, the solution has increased testing efficiency by a good 95 percent."
"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 solution works very well for test management and it also automates a lot of the testing functions so that you don't have to manage them in Excel spreadsheets."
"Tricentis qTest brought benefits by providing all test cases in one central repository with easy access."
"The biggest thing we've learned from this tool is the ease of using it."
"Overall, the solution has increased testing efficiency by about 60 percent, compared to what they were doing before."
"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."
 

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."
"I don't like that you need to use a lot of tabs. One test case takes 15-20 minutes and on Zephyr it takes about 5-10 minutes."
"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."
"Something that needs to improve is the model of the licensing. For instance, if you have two packs from two servers, you need to buy two licenses."
"They should work on integrating the solution with AI."
"Capability for scalability is basic, it's not as sophisticated as I would like."
"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."
"Right now, on a scale of one to five, I would say the Insights reporting engine is a three because we are facing some performance issues."
"The graphical reports, API integration with the customized automation test tools and support for the same need to be improved."
"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."
"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."
"Overall, it gets the job done, but it's a struggle to do it."
"We feel the integration between JIRA and qTest could be done even better. It's not as user-friendly as qTest's other features."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
 

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."
"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 a little over $1,000 for a concurrent license."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"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."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
893,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
34%
Computer Software Company
16%
Manufacturing Company
10%
Comms Service Provider
6%
Financial Services Firm
17%
Manufacturing Company
10%
Insurance Company
9%
Healthcare Company
8%
 

Company Size

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

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: April 2026.
893,311 professionals have used our research since 2012.