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
 

Categories and Ranking

TestRail
Ranking in Test Management Tools
2nd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
21
Ranking in other categories
No ranking in other categories
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
16
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Test Management Tools category, the mindshare of TestRail is 12.9%, down from 13.3% compared to the previous year. The mindshare of Tricentis qTest is 16.4%, up from 9.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.
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 solution is very stable. We've never had any issues with it."
"The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition."
"The product’s most valuable feature is the UI. The structure of test cases is easy to understand."
"Reliable and stable. It is important that TestRail be up and running 24/7 as we have users around the world using it."
"The API to support integration of the homemade automated testing tool."
"I haven't faced any stability issues using the solution. Stability-wise, I rate the solution a ten out of ten."
"The most valuable features are the reporting in the dashboard and the general way in which we can create test runs is helpful."
"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."
"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 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."
"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."
"The solution's real-time integration with JIRA is seamless."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"Works well for test management and is a good testing repository."
"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..."
 

Cons

"I've encountered at some point, some difficulties on the administration side, but I don't remember exactly what they were."
"It would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be."
"The test suite management has room for improvement as well as better reporting."
"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."
"Their customer support could be improved. Sometimes we struggle with that. It could be faster. Whenever we raise any query, they get back to you but the turnaround time is very slow."
"The product is not focused on synthetic data creation. I would also like to see more integrations with other platforms."
"Better prediction of text."
"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."
"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."
"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."
"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."
"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."
"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 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."
"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."
"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."
 

Pricing and Cost Advice

"Negotiate the best deal you can."
"The solution is quite reasonably priced for what it offers and offers a monthly subscription model."
"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."
"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."
"Pricing for small teams seems correct with respect to competitors."
"My advice to others is to shop around for the best deal. Some options out there are free in cyberspace."
"Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time."
"For the 35 concurrent licenses, we pay something like $35,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."
"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."
"We're paying a little over $1,000 for a concurrent license."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"It's quite a few times more costly than other tools on the market."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
829,541 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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?
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 expe...
 

Also Known As

TestRail by Gurock
qTest
 

Learn More

 

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: December 2024.
829,541 professionals have used our research since 2012.