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
18th
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (21st)
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Test Management Tools category, the mindshare of PractiTest is 2.6%, down from 2.6% compared to the previous year. The mindshare of Tricentis qTest is 16.1%, up from 10.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

DC
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.
Sudipto Dey - PeerSpot reviewer
It doesn't require installation because you can use it through the URL; it's user-friendly and has an excellent reporting feature
The support for Tricentis qTest has room for improvement. The response could be better. There's a feature I want to document on the Tricentis Idea Portal for Tricentis qTest, which I hope to see in the next version of the tool. It's a feature available in Micro Focus where you execute a test, and then on a spec level, you mark it as pass or fail. Then at the overall level, Micro Focus will automatically mark the test as a pass if all steps passed or failed, even if one step failed. However, here in Tricentis qTest, you still need to mark the overall level of the test cases. It's not automated, unlike what you have in Micro Focus. If Tricentis adds that feature in Tricentis qTest, it will make life easier for testers.

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."
"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..."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"Works well for test management and is a good testing repository."
"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 initial setup was very easy."
 

Cons

"It doesn't allow you to connect to multiple different tracking tools."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"qTest offers a baseline feature where you can only base sort-order for a specific story or requirement on two fields. However, our company has so many criteria and has so many verticals that this baseline feature is not sufficient. We would want another field to be available in the sort order."
"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."
"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 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."
"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."
"Could use additional integration so that there is a testing automation continuum."
 

Pricing and Cost Advice

"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
"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."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"We're paying a little over $1,000 for a concurrent license."
"It's quite a few times more costly than other tools on the market."
"Our license price point is somewhere between $1,000 and $2,000 a year."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
19%
Healthcare Company
8%
Retailer
6%
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
11%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
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?
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.
What needs improvement with Tricentis qTest?
Tricentis qTest needs improvement in its repositories' functionality. Unlike Azure, it does not have repositories to upload scripts. Additionally, it lacks features like task addition and tracking ...
 

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 2025.
845,040 professionals have used our research since 2012.