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."
"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 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."
"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."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"The most valuable feature of Tricentis Tosca is it is a completely scriptless automation tool, which I liked a lot. They keep on continuously improving their tools, wherever we are facing any challenges they are able to provide a solution for it. It is easy to learn, everyone can easily read and understand what is happening with the scripts. Any business user or function tester can use the tool efficiently. This is a complete solution package."
"For beginners, the product is good, especially for those who are interested in the quality side of software testing."
"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."
"This tool has test data management capability along with test management."
"The most valuable features of Tricentis Tosca are the Salesforce scanning. There are two scanning for Salesforce applications. There is Salesforce scanning and normal application scanning. Object identification has been really useful in Tricentis Tosca."
"It has helped teams within our organization become more aware of the testing requirements in terms of risk and priority."
"The most important feature is its ability to support the technical automation of specific clients that we cannot use with other tools."
"The technical support is good, we were satisfied."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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."
"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."
"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."
"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."
"They need to improve on the reports after the execution of automation tests, since all the current organizations are looking for detailed graphical reports."
"I would like to be able to manage different projects in one repository or have better data exchange between repositories."
"There should be ease of data manipulation within automation test cases."
"While the initial setup was straightforward, we required assistance with the configuration to ensure that everything was done correctly."
"The solution needs to improve its simulation of mobile environments. Right now, that aspect is really lacking."
"The solution should work with the Linux platform. Right now, it only runs on Windows."
"Security, UI, and basic performance improvements could be done to the product to enhance its use."
"They can make it more stable. I have used this tool for SAP applications. They have an alliance with SAP, and it mostly worked fine, but there were a few glitches. However, we got the required support from the Tricentis team. They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack."
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 UiPath Test 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.