No more typing reviews! Try our Samantha, our new voice AI agent.

Tricentis Tosca vs Tricentis qTest vs Zephyr Enterprise comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Featured Reviews

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.
reviewer2740515 - PeerSpot reviewer
Senior Software Engineer 2 at a tech services company with 51-200 employees
Automation test development becomes accessible and effective for functional testers
Tricentis Tosca is a codeless tool, making it easy for everyone to understand the transition of how to develop scenarios or test cases. In Tricentis Tosca, analyzing failures is straightforward because every time it fails somewhere, I get the screenshot, which helps me analyze how and why it failed. It has all the modules, including some pre-built ones that can be reused efficiently. Compared to other code tools such as Selenium, where I used to develop one script in one day, with Tricentis Tosca I can easily develop one script in four hours or three hours, saving four to five hours in a day.
JM
Director - Quality Engineering at a financial services firm with 501-1,000 employees
Integration with tool streamlines test management but needs better exporting options
I use it for test management within Jira This tool boasts an incredibly user-friendly interface that integrates seamlessly with other Jira tools. I particularly appreciate its intuitive features for designing test plans, creating test cases, and executing test cycles. Some areas for improvement,…

Quotes from Members

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

Pros

"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."
"Overall, the solution has increased testing efficiency by about 60 percent, compared to what they were doing before."
"The solution works very well for test management and it also automates a lot of the testing functions so that you don't have to manage them in Excel spreadsheets."
"It has taken us to the next level, in a very positive way, in the management of our overall test cases."
"Overall, the solution has increased testing efficiency by a good 95 percent."
"qTest has probably doubled our efficiency."
"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."
"Tricentis qTest brought benefits by providing all test cases in one central repository with easy access."
"Tosca is a low-code no-code automation tool, allowing direct automation and reusability of test cases."
"The amazing features provided by Tricentis takes automation to a different world and it's fun working with it."
"You can push transactions through to live, and you can intercept some transactions and return them back with mocked data."
"The product helps us to create very accurate test cases."
"The most valuable aspect of the solution is the extremely fast setup, as you can really get up and running within a very small window of time, and we like the fact that it works across mobile, desktop, web, and APIs, giving the solution a broad range of applications."
"The Model-Based Test Automation is the most valuable feature, where you can create reusable components. Even though we are using a scriptless automation tool, there still needs to be an understanding of how to create reusable components and how to keep refactoring and how to keep regression, the test scripts, at an okay level. We are coupling Tosca with some other risk-based testing tools, as well, but automation is primarily what we're using Tosca for, the scriptless, model-based technology which is driving automation for us."
"Improves the software quality in production by finding more defects with automated test sets, before transporting developments to production."
"It allows manual testers to pick up automation, because it is a scriptless tool."
"It's very simple to use, which is beneficial, and it has 90% of the basic features you need without having to pay a lot of extra money."
"Zephyr Enterprise is a stable solution."
"The solution does its job well."
"It has a very intuitive user experience."
"We use the solution for test case management."
"It has integration with test automation tools."
"Now, we are getting consolidated reports in one place, we have all our metrics and repository together, and this is helpful."
"Zephyr really improves the testing of the product on many levels - planning, test case creation, automation goals, test reporting, and verification of the testing."
 

Cons

"One of the things I noticed was the reporting part wasn't very good."
"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."
"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 support for Tricentis qTest has room for improvement. The response could be better."
"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."
"The Insights reporting engine has a good test-metrics tracking dashboard; the overall intent is good, compared to other test tracking or test management tools, but the execution is a little bit limited and the results are not consistent."
"The graphical reports, API integration with the customized automation test tools and support for the same need to be improved."
"Right now, on a scale of one to five, I would say the Insights reporting engine is a three because we are facing some performance issues."
"Primarily I'm dealing with customers looking for a cheap solution, and they are willing to try open-source automation solutions. So from this perspective, the price of Tosca is not as competitive."
"I would like to see more implementation of AI on the self-healing aspect."
"Tosca's reporting features could be better. Tricentis had a reporting tool called Analytics, but it didn't function properly after they reworked it. After that, they tried a new approach with key-tracing, and that didn't work."
"Product quality has declined as it grows, and its updates aren't without fault. The process of resolving problems has slowed, and as it expands into other areas like NeoLoad and other testing tools, the product becomes more complicated. It used to be a small firm with a clear goal, but as it grows, the quality has been affected."
"It may be different for other companies, but for us, establishing a set of procedures to get people trained was important."
"So far, all our issues have had to do with our unfamiliarity with the product."
"I would say the reporting part of the tool is an area of concern where improvements are required."
"Most of us have had the complaint that loop statements are missing, without which testing in reality was difficult, as many times test scenarios needed to be run in iteration and version 8.4 has included this feature."
"Additionally, they could improve the daily reporting. It does generate reports, but they are screen based reports."
"The reporting, and the ability to reorganize the test repository, which are a little stifling. There is definitely room for improvement there."
"We are looking for advanced support with integration to CI tools. This is something which Zephyr does not have today."
"The reporting, and the ability to reorganize the test repository, which are a little stifling. There is definitely room for improvement there."
"We would like support for the agile and behavior-driven development (BDD) approaches."
"The reporting, and the ability to reorganize the test repository, which are a little stifling. There is definitely room for improvement there."
"For JIRA, in comparison to other solutions, such as TestRail, Zephyr is good, but it is not as good as DFS."
"Creating better default varieties of reporting would make the product much better and more popular."
 

Pricing and Cost Advice

"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."
"It's quite a few times more costly than other tools on the market."
"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."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"The licensing cost for Tricentis Tosca is expensive. It has multiple features, but to use all of its features, you have to pay for additional licenses."
"Tricentis Tosca may be relatively on the higher side in terms of pricing, but their sales rep can give pretty decent deals when asked."
"I would like to see better costing packs. There are several features but USD $11,000 for one license is expensive."
"Licensing fees are paid on a yearly basis."
"Tricentis Tosca is an expensive solution and there is an annual license required. The whole licensing process is confusing and it could be made easier."
"A competitor of Tricentis Tosca: Katalon Studio, is very similar and offers lower pricing, though Tricentis Tosca offers more features and benefits."
"The price of Tricentis Tosca is approximately Є10,000 for one license. However, it used to be much cheaper, but they changed their license structure. It used to be a structure where if you bought a license you would receive one year of free support and maintenance. Now they only have a yearly license, and that is expensive."
"Pricing for Tricentis Tosca could be improved because it's very expensive."
"DFS is more expensive than Zephyr. DFS is around $32 per person, whereas Zephyr is $10 per person. There is a major difference in the price, which is the main reason why we are trying to shift to Zephyr."
"It costs a couple of thousand dollars for a little more than 125 users, per month."
report
Use our free recommendation engine to learn which Regression Testing Tools solutions are best for your needs.
885,376 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Insurance Company
9%
Healthcare Company
9%
Manufacturing Company
12%
Financial Services Firm
12%
Computer Software Company
10%
Retailer
6%
Financial Services Firm
21%
Computer Software Company
9%
Insurance Company
6%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise14
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise24
Large Enterprise72
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise5
 

Questions from the Community

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 a...
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 Trice...
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, centra...
How does Micro Focus UFT One compare to Tricentis Tosca?
We reviewed MicroFocus UFT One but ultimately chose to use Tricentis Tosca because we needed API testing. MicroFocus...
How does Tricentis Tosca compare with Worksoft Certify?
Tosca fulfills our business needs better because it is an end-to-end solution across technologies. We like that it is...
What do you like most about Tricentis Tosca?
For beginners, the product is good, especially for those who are interested in the quality side of software testing.
What needs improvement with Zephyr Enterprise?
Some areas for improvement, include its export capabilities. Exporting test cases, especially those with screenshots ...
What advice do you have for others considering Zephyr Enterprise?
I would recommend it mainly for manual testing and test management. Within Zephyrscale, they also have automated test...
 

Also Known As

qTest
Orchestrated Service Virtualization
SmartBear Zephyr
 

Overview

 

Sample Customers

McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
HBO, AMEX, BMW Group, ING, Bosch, Austrian Airlines, Deutsche Bank, Henkel, Allianz, Bank of America, UBS, Orange, Siemens, Swiss Re, Vodafone
Hyundai, Fujitsu, Google, David Jones, Burger King, Ingenico, Websense, Dow Jones, Harris, Saab
Find out what your peers are saying about Tricentis, Katalon Studio, OpenText and others in Regression Testing Tools. Updated: March 2026.
885,376 professionals have used our research since 2012.