Most Helpful Review
Helps us to quickly come up with a test plan, but overall, it's not as intuitive to use as it could be
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"The solution's real-time integration with JIRA is seamless."
"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."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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 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 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."
"It has helped teams within our organization become more aware of the testing requirements in terms of risk and priority."
"The solution is script-less, so you don't need IT knowledge to use the solution in an operational way. This is the most valuable feature. It's also only one of two or three tools that can do good automation on SAP, and in my opinion, it's the best of those."
"The Model-Based Test Automation is the most valuable feature, where you can create reusable components. Even though we are using a scriptless automation tool, there still needs to be an understanding of how to create reusable components and how to keep refactoring and how to keep regression, the test scripts, at an okay level. We are coupling Tosca with some other risk-based testing tools, as well, but automation is primarily what we're using Tosca for, the scriptless, model-based technology which is driving automation for us."
"This solution is easy to use for everybody, including those who are not IT-educated."
"Tosca BI is important to make sure that our data integrity is in check and validated; to make sure our data is good. Our data is the number-one important driver for our company, so if that's not good, we have some big problems."
"We like the fact that it works across mobile, desktop, web, and APIs. Due to this, the solution has a broad range of applications."
"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 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."
"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."
"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."
"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 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."
"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."
"Not being able to mask test data in relation to testing data management, in my opinion, is also a limitation."
"The solution should work with the Linux platform. Right now, it only runs on Windows."
"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."
"I would like to be able to manage different projects in one repository or have better data exchange between repositories."
"The main area where there is room for improvement is how they do upgrades. Going through this current upgrade, we were delayed a month because we are using a third-party tool. It's called Tosca Connect by Tasktop. When this latest upgrade broke that relationship between the two, it took Tricentis a month to come back with a workable solution... Their whole upgrade process needs to be better and cleaner, from an end-user standpoint."
"The solution needs to improve its simulation of mobile environments. Right now, that aspect is really lacking."
"I would like to see better integration with other testing tools."
"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."
Pricing and Cost Advice
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"It's quite a few times more costly than other tools on the market."
"We're paying a little over $1,000 for a concurrent license."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"We signed for a year and I believe we paid $24,000 for Flood, Manager, and the qTest Insights. We paid an extra for $4,000 for the migration support."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"Tricentis Tosca may be relatively on the higher side in terms of pricing, but their sales rep can give pretty decent deals when asked."
"We have around 200 [concurrent] licenses and the cost around $1.4 million a year."
"I am satisfied with the cost."
"My understanding is that it's an expensive product, although I don't know the specifics with regards to pricing."
Questions from the Community
Ask a question
Earn 20 points
Top Answer: From a reliability standpoint, we have Tosca setup with DEX to check some of our production apps to ensure they are up and running. We did this because we were noticing that some of our… more »
out of 32 in Test Management Tools
Average Words per Review
out of 44 in Functional Testing Tools
Average Words per Review
Compared 13% of the time.
Compared 10% of the time.
Compared 9% of the time.
Compared 9% of the time.
Compared 6% of the time.
Compared 12% of the time.
Compared 8% of the time.
Compared 8% of the time.
Compared 7% of the time.
Compared 5% of the time.
Also Known As
|QASymphony is a leading provider of enterprise test case management, test analytics and exploratory testing solutions for agile development and QA teams. Our solutions help companies create better software by improving speed, efficiency and collaboration during the testing process.|
Tricentis Tosca specializes in enabling large enterprises to improve the quality of their applications by equipping them to optimize, manage, and automate their software testing.
Tosca's model-based approach to software test automation enables enterprises to achieve high automation rates while maximizing business risk coverage.
Tricentis Tosca also provides market-leading test case design and planning capabilities, test data provisioning, service virtualization, mobile testing, and more.
Tosca is fully compatible with other testing solutions and Application Lifecycle Management products. Tricentis also offers uniquely designed testing solutions for SAP, ServiceNow, Trax, Avaloq, and Oracle.
Learn more about Tricentis qTest
Learn more about Tricentis Tosca
|Amazon, Salesforce, Barclays, Adobe, SecureWorks, Samsung, OfficeDepot, Zappos, Cisco, Visa, Verizon, FICO, Silverpop, Nordstrom||HBO, AMEX, BMW Group, ING, Bosch, Austrian Airlines, Deutsche Bank, Henkel, Allianz, Bank of America, UBS, Orange, Siemens, Swiss Re, Vodafone|
Computer Software Company29%
Financial Services Firm14%
Computer Software Company34%
Comms Service Provider14%
Financial Services Firm6%
Financial Services Firm35%
Computer Software Company41%
Comms Service Provider13%
Financial Services Firm7%
Tricentis qTest is ranked 3rd in Test Management Tools with 10 reviews while Tricentis Tosca is ranked 1st in Functional Testing Tools with 12 reviews. Tricentis qTest is rated 8.4, while Tricentis Tosca is rated 8.6. The top reviewer of Tricentis qTest writes "Provides a central point of reference for tracking bugs and failures, who owns the issue and its status". On the other hand, the top reviewer of Tricentis Tosca writes "Having a regression suite that we can run gives us a high level of confidence in the changes we are making". Tricentis qTest is most compared with Micro Focus ALM Quality Center, Cognizant ADPART, TFS, Zephyr Enterprise and TestRail by Gurock, whereas Tricentis Tosca is most compared with Micro Focus UFT One, SmartBear TestComplete, Worksoft Certify, Selenium HQ and Katalon Studio. See our Tricentis Tosca vs. Tricentis qTest report.
See our list of .
We monitor all Test Management 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.