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."qTest helps us compile issues and have one place to look for them. We're not chasing down emails and other sources. So in the grand scheme of things, it does help to resolve issues faster because everyone is working off of the same information in one location."
"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."
"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."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"Compared to other tools we have been looking at, you don't have to be a programmer to operate it, though it helps. It also a product that can be used by business people."
"The initial setup isn't too difficult."
"It has helped teams within our organization become more aware of the testing requirements in terms of risk and priority."
"The automation engine is very strong, and it is very competitive in the market in terms of features. They develop a lot of features."
"Tricentis Tosca is a really cool tool that you don't have to be technical to use it. Additionally, the solution is easy to use. The modules, libraries, and reusable are in an efficient way to update all the tests. I find it spot on with that. We also started using the design which we switched from Excel. The design was superior to Excel."
"The mainframe testing and UI automation are the most valuable aspects of the solution."
"Very user-friendly and the low code automation is really helpful."
"I am impressed with the product's script test."
"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."
"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."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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 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."
"I would like to see more implementation of AI on the self-healing aspect. That would be like the next step."
"It would be of great help if they can fix the loading or performance issues. Sometimes, when I create the test case folder and test cases, it feels like it has loading or performance issues. When passing the objects, we can't sometimes find the exact element. We need to find out that exact location and just give the path for that, and then it works. In the pipeline, when creating Jenkins, we create the list execution for passing the execution list to the commander. I feel it is a bit late, by a fraction of seconds. I first thought it could be my mistake or a setting issue, but I worked on that, and it's not a mistake or a setting issue."
"The document object model or some aspects of it has a bit of a learning curve."
"Tricentis Tosca could improve on its mobile automation solution."
"Tricentis Tosca currently does not support any mobile testing and can be improved."
"One thing to improve in Tricentis Tosca is that it's not compatible with Excel based forms. Another area for improvement is that the tool is not compatible with OpenText applications. The support and licensing cost for it also need improvement. The tool also needs cloud support, as it's currently on-premises only."
"The reporting function was lacking in usability and detail."
"It can be quite expensive."
Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews while Tricentis Tosca is ranked 1st in Regression Testing Tools with 98 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 Katalon Studio, OpenText UFT One, Worksoft Certify, Postman and Oracle Application Testing Suite. 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.
