We performed a comparison between Tricentis qTest and Tricentis Tosca based on real PeerSpot user reviews.
Find out in this report how the two Regression Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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 solution's real-time integration with JIRA is seamless."
"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..."
"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 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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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 item that is different from all the other tools is that it's module based."
"The most valuable features of Tricentis Tosca are all the test automation functionality. It is a full-scale automation tool."
"I am impressed with the product's script test."
"It is easy to maintain and easy to automate. No coding skills are required to automate. It is also easy in terms of transferring knowledge and skills. Many of my team members shifted over the past one and a half years, and there was no big issue with respect to knowledge sharing. It is a good tool that enables me to re-automate my scripts and update my scripts as quickly as possible. Looking at the amount of rework and maintenance activity that we had done for our scripts, it might have been a nightmare with some other scripting tool."
"The reporting is really nice."
"Software testing tool that has multiple features. It's good to use for SAP testing, and it helps reduce test execution time."
"Multiple scanning engines to automate many different applications."
"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."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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."
"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."
"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 a better user interface."
"The Test Management options are still weak - improvement is outlined, but not yet visible. I"
"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."
"Tricentis Tosca's performance could be better. Sometimes when we are remapping or when it is loading it can take a lot of time. There are free solutions that have better performance in this area."
"Tricentis Tosca could improve on its mobile automation solution."
"There have been some setbacks because of upgrades. While Tosca has been around for a while, Tricentis has catered to smaller clients and I don't think they have done such a large, at-scale transition or transformation before or worked with a company like ours, which is doing an enterprise-wide transformation. When we go to their customer advisory-board meetings, upgrades have been an issue. They have been working a lot to make upgrades seamless."
"Tricentis Tosca’s technical support could be improved."
Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews while Tricentis Tosca is ranked 1st in Regression Testing Tools with 96 reviews. Tricentis qTest is rated 8.4, while Tricentis Tosca is rated 8.2. The top reviewer of Tricentis qTest writes "Puts all our test cases in one location where everyone can see them. qTest also allows the segregation of different types of Testing". On the other hand, the top reviewer of Tricentis Tosca writes "Does not require coding experience to use and comes with productivity and time-saving features ". Tricentis qTest is most compared with OpenText ALM / Quality Center, TestRail, Zephyr Enterprise, TFS and Panaya Test Dynamix, whereas Tricentis Tosca is most compared with OpenText UFT One, Katalon Studio, Worksoft Certify, Postman and Tricentis NeoLoad. See our Tricentis Tosca vs. Tricentis qTest report.
See our list of best Regression Testing Tools vendors.
We monitor all Regression Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
