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

Tricentis Tosca vs Tricentis qTest 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:
 

Categories and Ranking

Tricentis qTest
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
Test Management Tools (3rd)
Tricentis Tosca
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
112
Ranking in other categories
Service Virtualization (1st), Functional Testing Tools (1st), Mobile App Testing Tools (1st), Regression Testing Tools (1st), API Testing Tools (2nd), Test Automation Tools (1st)
 

Featured Reviews

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.
PrabhuKrishnamoorthy - PeerSpot reviewer
Has transformed testing by reducing scripting effort and enhancing productivity with advanced features
The self-healing feature of Tricentis Tosca needs significant improvement. Currently, it is static and not dynamic. For example, if a button in an application changes, Tricentis Tosca should be smart enough to detect the change and still execute the script seamlessly. Improvements are needed to ensure it responds dynamically to changes in the application.

Quotes from Members

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

Pros

"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."
"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."
"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..."
"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."
"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 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."
"The self-healing aspects and maintenance of scripts are much faster and quicker, and we are able to find better avenues and better productivity in terms of maintenance, which we can pass on to the customer."
"UI and UX are pretty easy to understand without much of a problem."
"I face no challenges or stability issues."
"We are satisfied with the support of Tricentis."
"The feature that I have found the most valuable is the recovery and cleanup process. Suppose there is a list of test cases and one test case has failed, it should not impact the other test cases. We can reuse the same test case. We can change the configuration of parameters and then use the test cases on the same thing. So, that's a useful thing. Otherwise, we have to use the cleanup process. Another useful feature is to have our own library files. We can create our objects in the libraries and reuse them. There is no need to create duplicate data for that. They have been giving some enhancements recently which means integration is also there. They've integrated with different software like Jenkins, Bamboo. So, we can also create pipeline points. They have recently given SAP and everything, which is very useful."
"The product's initial setup phase was easy."
"The platform's most valuable feature is model-based testing, which is effective for test case design and optimization."
"To me, what stands out the most about Tricentis Tosca is that even if I'm not a technical tester, I could pick up on how to use it very quickly because of the mechanisms of the tool, for example, its scanning mechanism. I'm not so technical, but I'm able to maneuver through Tricentis Tosca and derive capability. It's a user-friendly tool. It's not very complex."
"The mainframe testing and UI automation are the most valuable aspects of the solution."
"The reporting is really nice."
 

Cons

"For UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available."
"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."
"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."
"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 support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"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."
"Security, UI, and basic performance improvements could be done to the product to enhance its use."
"The document object model or some aspects of it has a bit of a learning curve."
"The user management could improve in Tricentis Tosca because it is confusing. It would be better to have it in one place. Having to add it to the cloud and to a specific project can be a mess."
"They need to improve on the reports after the execution of automation tests, since all the current organizations are looking for detailed graphical reports."
"Many times when we have raised a ticket, we did not get an urgent response."
"The issue is that even though the components are tightly integrated, object identification can be quite slow, sometimes taking five to ten seconds."
"It requires some coding customization that requires expertise."
"A disadvantage of Tricentis Tosca is that you have to customize it according to your need, during the early stages of the software, particularly during upstream testing, before system and unit testing."
 

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."
"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."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"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 $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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."
"The tool's pricing is lower than that of other automation tools."
"I'm not sure if I'm at liberty to talk about the pricing, but it has some significant costs. For example, you have to pay a license and maintenance fee. Then the rest of the terms are negotiable. We have to consider what we need and what benefit we get from it."
"I rate the price of Tricentis Tosca a two out of five."
"I would rate the pricing a seven out of ten, where one is cheap, and ten is expensive. It is on the higher side."
"Tricentis Tosca is an expensive tool and the licensing is not simple."
"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."
"A yearly license costs around 20,000 euros."
"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."
report
Use our free recommendation engine to learn which Regression Testing Tools solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

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

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?
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...
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 UFT is a performance and functional testing tool. We tested it, and it was well...
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 scriptless, so even non-experienced staff can use it. To put it simply, with To...
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.
 

Also Known As

qTest
Orchestrated Service Virtualization
 

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
Find out what your peers are saying about Tricentis Tosca vs. Tricentis qTest and other solutions. Updated: February 2023.
865,295 professionals have used our research since 2012.