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 (23rd)
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 PractiTest is 3.0%, up from 2.2% 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%
PractiTest3.0%
Other88.3%
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

"The most valuable feature is the way the libraries are structured so that they were not folder driven."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"Works well for test management and is a good testing repository."
"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."
"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."
"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."
"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."
"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

"It doesn't allow you to connect to multiple different tracking tools."
"Could use additional integration so that there is a testing automation continuum."
"We faced challenges when trying to consolidate data in a repository, and similar features were lacking in qTest. It also does not allow for task tracking or calculating time spent on tasks, which affects project timelines."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"The support for Tricentis qTest has room for improvement. The response could be better."
"For UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
"We're paying a little over $1,000 for a concurrent license."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"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."
"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."
"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.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Government
9%
University
7%
Manufacturing Company
7%
Financial Services Firm
17%
Manufacturing Company
11%
Healthcare Company
10%
Insurance 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: December 2025.
881,082 professionals have used our research since 2012.