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."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 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."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"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 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 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."
"Works well for test management and is a good testing repository."
"This solution is very easy to learn and any non-programmer or manual tester, with little experience in automation, can pick it up quite easily."
"The most valuable features of Tricentis Tosca are the ease of use, you do not need to program if you do not want to."
"The item that is different from all the other tools is that it's module based."
"I face no challenges or stability issues."
"We have to automate thousands of test cases and complete end-to-end SAP on business processes. To manually execute these tasks, it would take us at least two months. By automating these tasks using Tosca, now it takes five to 10 days maximum. Tricentis Tosca is a codeless or scriptless automation tool."
"This tool is very easy to use and I think that anyone can come in, having no experience with it, and within four to six months be comfortable with it."
"The low code is the best feature."
"Software testing tool that has multiple features. It's good to use for SAP testing, and it helps reduce test execution time."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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."
"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."
"Many times when we have raised a ticket, we did not get an urgent response."
"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."
"Parallel execution is not yet implemented for Tosca. This means you can't execute the same test case on multiple machines remotely."
"It needs better integration with JIRA."
"The product needs to improve object identification. The identify with properties and anchor methods work perfectly, while the by-index and image methods may face challenges."
"Setup wasn't that straightforward; it was more complex. It all depends on the environment, because there were a lot of errors on our applications. Therefore, it wasn't an easy setup for us."
"ScratchBook execution needs to be improved as Tosca crashes multiple times."
"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 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.