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."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."
"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 solution's real-time integration with JIRA is seamless."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"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."
"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."
"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..."
"Software testing tool that has multiple features. It's good to use for SAP testing, and it helps reduce test execution time."
"The solution has plenty of features compared to other solutions."
"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 automation engine is very strong, and it is very competitive in the market in terms of features. They develop a lot of features."
"The initial setup isn't too difficult."
"The model-based scriptless automation is the most valuable feature because it needs less maintenance as compared to script-based automation."
"I face no challenges or stability issues."
"We are satisfied with the support of Tricentis."
"Reporting shouldn't be so difficult. I shouldn't have to write so many queries to get the data I'm looking for, for a set of metrics about how many releases we had. I still have to break those spreadsheets out of there to get the data I need."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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."
"Could use additional integration so that there is a testing automation continuum."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"There should be ease of data manipulation within automation test cases."
"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."
"The support we received from Tricentis Tosca was good, but it can improve."
"Security, UI, and basic performance improvements could be done to the product to enhance its use."
"I think the downside would be licensing costs which are very high."
"While the initial setup was straightforward, we required assistance with the configuration to ensure that everything was done correctly."
"In terms of areas for improvement, Tricentis has a variety of tools, even its test management tool called qTest. Tricentis Tosca does have integration with different Tricentis tools, but the integration is geared towards a larger organization perspective. For very small organizations that have minimal licenses, the integration needs to be improvised. For example, I belong to a smaller organization that has only one license, so the capability that the tool provides for integration isn't sufficient because my company needs to have separate workspaces. When Tricentis Tosca is going to be running, it is going to use that license, but my company wants another separate workspace to record, relay, and test. This is what my team has been struggling with, and the mechanism is probably there, but that needs more time and investigation, so I can't say that I'm one hundred percent certain that Tricentis Tosca, in terms of integration for a smaller organization is insufficient. Another area for improvement is that Tricentis Tosca is currently just a Windows-based tool which affects the market because nowadays, Windows isn't the only operating system, for example, there's also Apple or IOS that's moving much faster than Windows."
"The tool lags in client-based applications. We have also encountered issues with the features in integrations."
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.