We performed a comparison between Micro Focus UFT One and Tricentis Tosca based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison of Results: Based on the parameters we compared, Tricentis Tosca seems to be a superior solution. All other things being more or less equal, our reviewers found that Micro Focus UFT One’s automation capabilities could be improved.
"UFT is very strongly built. It's widely used, so there's a lot of support."
"Has improved our organization by allowing us to obtain fast, detailed information about the behavior of our products and to supply this to the customer, enabling us to work together without the need for special programming knowledge."
"It is easy to automate and new personnel can start learning automation using UFT One. You don't have to learn any scripting."
"Object Repository Technology, which is a good mean to identify graphical components of the applications under test."
"One advantage of Micro Focus UFT is that it is more compatible with SAP, Desktop ECC SAP, than S/4HANA."
"The initial setup is relatively easy."
"It is very simple to use, and the scripting language is even easier."
"It's simple to set up."
"The use of automation is most valuable."
"The most valuable feature of Tricentis Tosca is the Tosca Commander. Functionality is another thing I find most valuable in the solution."
"With one click, it will scan all the elements on the screen, so that the user can select the required elements for automation tests."
"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."
"We have multiple applications, and it supports parallel execution. It has mobile automation."
"One notable feature is its ability to handle negative XPath healing processes. If one XPath fails, Tosca can utilize backup XPaths to ensure test cases do not fail due to locator issues, thereby focusing on identifying application-side issues, which is the ultimate goal."
"Multiple scanning engines to automate many different applications."
"We can also create customized functions. For example, if something isn't supported in Tricentis Tosca Commander, we can create our own function to integrate it with Tosca Commander, so we can utilize it and integrate with the macros."
"The artificial intelligence functionality is applicable only on the web, and it should be expanded to cover non-web applications as well."
"I'd like to see test case-related reports included in the solution."
"There is a lot of room for improvement when it comes to friction-free continuous testing across the software life cycle, as a local installation is required to run UFT."
"Sometimes, the results' file size can be intense. I wish it was a little more compact."
"It doesn't support Telerik UI controls and we are currently looking for a patch for this."
"One area for improvement is its occasional slowness."
"The AI feature needs improvement. For banking applications, we input formatted text from documents, but the AI feature is recognizing three fields as one field, e.g., for a phone number, it puts all 10 digits in the international code or country code. Then, the script fails."
"The product wasn't easy for developers to learn and pick up in the area revolving around scripting for automation, and there was a lot of resistance from developers, causing my company to rely on specialist resources."
"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."
"I would like to see more implementation of AI on the self-healing aspect. That would be like the next step."
"First, Tricentis could improve Tosca's Linux scripting. We can automate Linux scripting, but there are a few commands that Tosca doesn't support. DVS support and the object identification mechanism could also be better."
"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."
"There should be ease of data manipulation within automation test cases."
"I would like to be able to manage different projects in one repository or have better data exchange between repositories."
"Tricentis Tosca currently does not support any mobile testing and can be improved."
"Security, UI, and basic performance improvements could be done to the product to enhance its use."
OpenText UFT One is ranked 2nd in Mobile App Testing Tools with 89 reviews while Tricentis Tosca is ranked 1st in Mobile App Testing Tools with 97 reviews. OpenText UFT One is rated 8.0, while Tricentis Tosca is rated 8.2. The top reviewer of OpenText UFT One writes "With regularly occurring releases, a QA team member can schedule tests, let the tests run unattended, and then examine the results". 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 ". OpenText UFT One is most compared with OpenText UFT Developer, Katalon Studio, SmartBear TestComplete, UiPath Test Suite and Ranorex Studio, whereas Tricentis Tosca is most compared with Katalon Studio, Worksoft Certify, Postman, SmartBear TestComplete and Testim. See our OpenText UFT One vs. Tricentis Tosca report.
See our list of best Mobile App Testing Tools vendors, best Regression Testing Tools vendors, and best API Testing Tools vendors.
We monitor all Mobile App 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.
Both products are very useful but it really depends on what you need to test and who is building the tests. We recently chose UFT One over Tosca in a specific use case where identifying images inside a map was needed. UFT uses both OCR and Image recognition where in Tosca you would have to identify specific pixels and those pixels could move depending on what device you were using.
From a test building perspective, I feel it is easier to build tests in UFT One than in Tosca. UFT One also gives you the ability to develop tests by either writing code or using the record and convert to code option (Allows developers and Business users to work together to build/update the same test).
If you can provide more info on what you are testing and your key drivers, I can try and give more info on what tool may be best.
We reviewed MicroFocus UFT One but ultimately chose to use Tricentis Tosca because we needed API testing.
MicroFocus UFT is a performance and functional testing tool. We tested it, and it was well suited for CI integrations. We liked it, in particular, because it integrates greatly with other platforms, like .net, QC and Jenkins. An added advantage was the multi-device support.
One of the best advantages of MicroFocus is that it integrates with legacy web technologies and even Windows client applications. Finally, MicroFocus supports cross-browser testing. Regardless of many features, including a test combinations generator and insight recording, it is relatively easy to learn.
That being said, it doesn’t support multiple formats of reporting. For now, UFT only supports exporting reports in HTML or PDF. MicroFocus should allow exporting to Excel, CSV, XML, and other formats. There is a bit of performance degradation of the test environment when executing automation scripts continuously for a long time. The execution can be inconsistent sometimes, and scripting takes a long time. Another downside is the high licensing price.
Tricentis Tosca is an integrated testing solution that includes testing automation and case design approach, risk-based testing, test data management, and service virtualization. The best feature is its versatility in helping both web and desktop applications. It is very reliable and stable. Another great feature is that you can reuse test cases.
The platform supports multiple technologies and devices. It is truly end-to-end. Because it is scriptless, anyone can learn to use it.
As much as we like it, there are downsides to Tosca, too. The price is one of them. It runs a bit expensive, but it is worth it. The test design section is complicated to learn, and the UI takes time to get used to.
Conclusions
Tosca is a better solution in terms of usability and versatility. MicroFocus is better for organizations with legacy web applications.