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
7.3
Number of Reviews
22
Ranking in other categories
No ranking in other categories
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 July 2025, in the Test Management Tools category, the mindshare of TestRail is 11.2%, down from 13.5% compared to the previous year. The mindshare of Tricentis qTest is 15.2%, up from 11.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
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

"The product’s most valuable feature is the UI. The structure of test cases is easy to understand."
"The features that I have found most valuable are that there are various test case templates and test artifact maintenance."
"The biggest advantage of using TestRail is its simplicity and intuitive interface."
"Integration with Confluence and JIRA."
"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."
"Most valuable features are the ease of organizing test cases and a great API for sending results from automated test run results into the database."
"The API to support integration of the homemade automated testing tool."
"I was on the lookout for automation testing on the browser and I believe this tool is very interesting in that matter. The solution is useful for UI testing. You just need to add the URL that is to be checked."
"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..."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"Works well for test management and is a good testing repository."
"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."
"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."
"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."
 

Cons

"It would be nice if they would add an export to Word."
"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."
"There are a number of improvements that have been requested. While I don't have a list of these requests available, many can be found on Gurock's forum."
"It would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be."
"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."
"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."
"TestRail's user interface is not great. When you use it for the first time, you will be very uncomfortable and not know how to create test cases. It doesn't have a field for preconditions and post-conditions."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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 JIRA integration with qTest needs to mature a lot... We need smarter execution with JIRA in the case of failures, so that the way we pull out the issues again for the next round is easy... Locating JIRA defects corresponding to a trait from the test results is something of a challenge."
"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."
"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."
"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."
 

Pricing and Cost Advice

"The solution is quite reasonably priced for what it offers and offers a monthly subscription model."
"My advice to others is to shop around for the best deal. Some options out there are free in cyberspace."
"I give the price a five out of ten."
"Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time."
"Negotiate the best deal you can."
"Pricing for small teams seems correct with respect to competitors."
"Its price is definitely not more. If they introduce automation, they can charge more."
"The product has a reasonable price in terms of the features."
"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 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."
"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."
"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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
10%
Manufacturing Company
10%
Healthcare Company
7%
Financial Services Firm
12%
Manufacturing Company
12%
Computer Software Company
12%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
TestRail lacks the functionality to map test cases to requirements and risks. While integration with another tool is a workaround, it doesn't fully meet my needs. Additionally, I would appreciate A...
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

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: June 2025.
860,592 professionals have used our research since 2012.