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

TestRail 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

TestRail
Ranking in Test Management Tools
2nd
Average Rating
8.0
Reviews Sentiment
6.1
Number of Reviews
23
Ranking in other categories
No ranking in other categories
Tricentis qTest
Ranking in Test Management Tools
3rd
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2025, in the Test Management Tools category, the mindshare of TestRail is 10.5%, down from 13.8% compared to the previous year. The mindshare of Tricentis qTest is 14.6%, up from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Market Share Distribution
ProductMarket Share (%)
TestRail10.5%
Tricentis qTest14.6%
Other74.9%
Test Management Tools
 

Featured Reviews

StuartBarker - PeerSpot reviewer
A tool that provides effective test management and real-time reporting capabilities
I have faced some issues with the integration between TestRail and Jira where the status of tests is not displayed (in Jira) due to I suspect security settings on the browser. In a large corporate environment, it is not easily changed. The support wasn't particularly helpful. It would be great if I could create custom reports, ideally with a tool designed specifically for that.
SamuLehikoinen - PeerSpot reviewer
Efficient and collaborative software testing providing comprehensive test management capabilities, seamless integration with various tools and impressive manual regression testing features
The user interface has a somewhat outdated design, which is certainly an area that could be improved. Some of the modules appear to be loosely connected, but despite these aspects, our overall experience with the tool was positive. When you begin integrating your testing tools with qTest, the available examples may not be very clear, and I believe this is an area that could be enhanced, particularly in terms of providing clearer integration guidance. While the tool's integration with various testing tools is impressive, there is room for improvement in showcasing more cases and benefits, especially through additional videos and documentation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"From a testing perspective, the management is awesome. I am able to do testing and then add the reporting and the evidence. It is fair in terms of the price that you're paying. You get what you're paying for."
"The most valuable features are the reporting in the dashboard and the general way in which we can create test runs is helpful."
"The feature that I have found most valuable is the dashboard."
"I haven't faced any stability issues using the solution. Stability-wise, I rate the solution a ten out of ten."
"I use the solution for test management."
"The API to support integration of the homemade automated testing tool."
"The ability to time test runs gives the tester the ability to compare calculated times to actual times it takes for a test case to run."
"This is a user friendly solution."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"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."
"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..."
"The solution's real-time integration with JIRA is seamless."
"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 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

"Customer support could be enhanced. All the support is provided via chat and emails. Sometimes, you really need to speak to a person, and arranging such calls is not easy."
"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."
"It's not easy to create a custom report. It's not straightforward. A good improvement would be if there was a way to report and create a custom report without using a plugin or scripting language."
"The platform needs improvement regarding performance and creating links."
"It would be useful if it had its own issue management system. At the moment, it's purely a test management tool and you have to link to a defect management tool, like JIRA. It would be useful if there was an option to use its own defect management tool so that it's integrated and not two separate tools."
"Better prediction of text."
"I do see room for lots of improvement in it. In terms of usability, duplication with test cases and constant creation of projects isn't easy. There is also too much API integration into automation tools, which is not there in ALM with UFT. Instead of setting it up as a project and using it, we set it up as a system for usability. It also lacks in the traceability aspect. For traceability, you need to use the JIRA plugin and drag traceability on JIRA, but the functionality is still quite limited. The biggest gap is mainframe testing. It would be good if I could start with mainframe testing. Manual granting of access is another issue. There is no API that I could use with another system where it is automated. There is an API for loading somebody to a project but not for adding to the application."
"TestRail should improve its pricing."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"For UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"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."
"The support for Tricentis qTest has room for improvement. The response could be better."
 

Pricing and Cost Advice

"The product is not much expensive."
"Its price is definitely not more. If they introduce automation, they can charge more."
"Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time."
"The product has a reasonable price in terms of the features."
"The price of the solution is based on how many users you have per year. When you grow, it is segmented, For example, 10 to 25, you have a price, and more than 50, or 100, you need to take the enterprise license. I don't think we will reach this point."
"I give the price a five out of ten."
"Negotiate the best deal you can."
"The solution is quite reasonably priced for what it offers and offers a monthly subscription model."
"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."
"We're paying a little over $1,000 for a concurrent license."
"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."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"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."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
867,497 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Manufacturing Company
11%
Financial Services Firm
9%
Insurance Company
7%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
10%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise3
Large Enterprise4
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise13
 

Questions from the Community

What is your experience regarding pricing and costs for TestRail by Gurock?
Pricing is reasonable for TestRail. It offers good value for money.
What needs improvement with TestRail by Gurock?
In TestRail, there is significant difficulty with roles and rights. They are not in the mainstream. The person who has the license has all the rights, which is understandable, but TestRail needs to...
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?
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?
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 looki...
 

Also Known As

TestRail by Gurock
qTest
 

Overview

 

Sample Customers

Apple, Microsoft, Boeing, Intel, NASA, Amazon, HP, Samsung
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about TestRail vs. Tricentis qTest and other solutions. Updated: September 2025.
867,497 professionals have used our research since 2012.