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

PractiTest 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

PractiTest
Ranking in Test Management Tools
17th
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (22nd)
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 March 2026, in the Test Management Tools category, the mindshare of PractiTest is 3.0%, up from 2.4% compared to the previous year. The mindshare of Tricentis qTest is 7.8%, down from 15.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Mindshare Distribution
ProductMindshare (%)
Tricentis qTest7.8%
PractiTest3.0%
Other89.2%
Test Management Tools
 

Featured Reviews

DC
Test Team Lead at a computer software company with 501-1,000 employees
Flexible and intuitive with easy reporting, and good support that is instantly available through chat
It doesn't allow you to connect to multiple different bug tracking tools at the same time. This is not an issue if you only have one bug tracker but we can potentially use different tools for different projects. As an example, if you connect PractiTest to Jira for one project, that's the one you have to use for all projects. We had a requirement to connect with Jira for one project, and a different tool for another, project but it was unable to accommodate that unfortunately. I would therefore like to see it easier to integrate with bug tracking tools at project level which would give each project the opportunity to use a different bug tracker if required.
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

"Since we started using this product, our organization's testing functionality has really improved."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
"PractiTest gives us the opportunity to control the testing process efficiently and saves us a lot of time that we had to spend while using other tools."
"This is a good solution for a global transnational company."
"In addition, we found PractiTest very user-friendly and customizable."
"Helped organise the manual test cases so they were documented correctly, which was invaluable as it allowed for reviewing and improving of test scripts so they could be followed by a number of different people which helped with resourcing."
"Converting a couple of these test plans into PractiTest was amazing and made a world of difference."
"Technical support of PractiTest is awesome. They are always ready to help in any time zone, which makes them stand out from others."
"On a weekly basis, for reporting it has definitely saved at least 50 percent of our time, if not more."
"The biggest thing we've learned from this tool is the ease of using it."
"The solution's real-time integration with JIRA is seamless."
"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."
"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."
"It is the single source for repository and traceability."
"It has taken us to the next level, in a very positive way, in the management of our overall test cases."
 

Cons

"It doesn't allow you to connect to multiple different bug tracking tools at the same time."
"It does not offer server installation, only software as a service."
"There are some features that I would like added: an option to export a part of tests with steps."
"Yes, there are times when server is very slow in response."
"It doesn't allow you to connect to multiple different tracking tools."
"Needs to improve adding the ability to run tests multiple times and setting different parameters."
"PractiTest practically requires a lot of sandboxing, demos with their team, and online tutorials."
"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."
"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 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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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 graphical reports, API integration with the customized automation test tools and support for the same need to 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."
 

Pricing and Cost Advice

"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"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."
"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."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
885,264 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Government
11%
University
7%
Manufacturing Company
7%
Financial Services Firm
16%
Manufacturing Company
10%
Insurance Company
9%
Healthcare Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise4
Large Enterprise1
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise14
 

Questions from the Community

Ask a question
Earn 20 points
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

Canonical, SAS, Amobee, Play Buzz, Abbott, Aternity, Zerto, Freeman
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about PractiTest vs. Tricentis qTest and other solutions. Updated: March 2026.
885,264 professionals have used our research since 2012.