Tricentis Tosca Reviews

The model-based scriptless automation is the most valuable feature because it needs less maintenance as compared to script-based automation.

Tricentis Tosca supports 35 technologies, such as web, mobile, Salesforce, Java, SAP, ServiceMax, and Flash applications.

Tosca follows the shift-left approach. A new resource can start automation on the first day of its project.

Parallel execution is not yet implemented for Tosca. This means you can't execute the same test case on multiple machines remotely. For execution, test cases have to be present on that machine. Even while, a test case is executed you can't perform any other activity; you end up sitting idle during execution.

I have used this solution for 18 months.

There were no stability issues.

There were no scalability issues.

Technical support is fair.

Previously, we were using Selenium. We switched to Tosca due to the less maintenance aspect and the wide technology support which it provides.

Configuration is easy.

No idea about the licensing cost.

Whilst selecting a vendor, we look for factors such as technical support and maintenance.

If you are looking for automation of the packaged application and less maintenance, then go for Tosca.

The most valuable feature is the UI-based interface for building modules and turning modules into test cases.

It greatly accelerated regression testing cycle via automated regression.

Upgrading from one version to another requires maintenance and rework in existing scripts. This is too much for my taste.

We have been using this since 2013.

There were no issues with stability.

We had to do extensive customization on top of their CI/Distributed Execution engine in order to integrate this into our Continuous Delivery pipeline.

Technical support is excellent.

This was my first automated testing tool.

The initial setup can be quite complex and training is required.

It's not cheap, but you get what you pay for.

We evaluated several other options which included all the most popular automated testing tools.

Be sure you are ready to support it earnestly with training and focus. If you do that, then it is worthwhile.

Ability to test Java Swing UI on business application.

It was the only way to organize and support automation testing process for our re-insurance tool for underwriters.

Browser compatibility (probably solved in the newest versions).

Version 8 of Tosca had weak compatibility with automation via browsers. Firefox and IE produced issues, unexpected quits during execution of automation test, and during automated clicks at elements. Also, execution of tests was possible at one thread only (at the same time other instruments for automation, like Selenium, allow using multiple threads). But probably some of mentioned problems are not actual for up to date versions of Tosca.

No issues.

Not all of UI elements were managed correctly by regular Tosca functions, we was forced to use Custom Controls for doing that.

Eight out of 10.

A bit complex.

We were forced to use a custom version of IBM Java and custom controls for managing of Java Swing UI elements. Some time was required to understand how to link all this stuff with Tosca (most of our questions were ultimately answered in Tosca documentation). Time for first setups was three to four hours, per employee’s laptop, but after some attempts it was shortened to one hour.

Yes I can recommend Tosca, especially for Java Swing applications.

AutoIt.

• Scriptless automation
• Ease of using
• Object Identification Wizard
• Business parameters
• Steering controls

• Our organization is completely based on automation of the activities.
• All the projects based on different technologies, such as SAP and Salesforce, are automated using Tosca.
• SMEs just need to run the scripts developed by automation testers to validate the intended behavior.
• We also use batches to schedule automation activities, which does not need any user attention.
• Hence, automation testers can run the scripts as well as work on the new work at the same time, resulting into increased productivity.

Security, UI, and basic performance improvements could be done to the product to enhance its use.

Six months.

No.

No.

Good.

Selenium WebDriver requires good skillset of coding. However, TOSCA is scriptless, hence anyone can learn it easily.

The online training material offered by Tricentis is very straightforward to get started with it.

The pricing is high, but altogether it offers you the ability to automate all sorts of applications: desktop, web, mobile, etc.

Yes. Selenium WebDriver and QTP.

I will recommend using TOSCA to all users who want to automate their applications or who want to work daily without any hassle.

Tosca Testsuite is a model based automation tool and it doesn't require an explicit framework, unlike other automation tools.

Tosca very efficiently helps us manage the time taken for automation, its very user-friendly and easy to work with.

I feel that the Tosca tool should be improved for handling Siebel applications. My team has tried the automation for a few different types of applications with Tosca. One of them was a Siebel application. We faced the most difficulties in the automation of that Siebel application. Tosca doesn't handle Siebel applications as well as it handles other platform applications. We had to try a lot of workarounds to complete the automation. That was one issue we faced when we worked with Tosca.

Almost 10 months.

There are very minor issues. They can be easily resolved.

Tosca Testsuite is very reliable and stable.

Not much. I Haven't faced any such issues until now.

The support team of Tricentis is really excellent. The support portal and the support teams work and help is really appreciated.

I prefer TOSCA over other tools.

The initial setup was not that easy or not that complex. I can say it was moderate.

It was in-house.

TOSCA Testsuite is a very good automation tool. It supports a wide variety of application automation. This tool provides a very efficient way of automation and also it is compatible with many other tools involved in the testing process like Quality Center, etc.

I mostly use the TOSCA Commander to create test cases. I also utilize the Tbox feature to automate complex test scenarios. Lastly, I find the requirements linking very useful in analysis after a release (i.e. test coverage, etc.).

The product is very useful in keeping track of test execution and coverage. This is because it has a feature called Execution List which shows resources and the test cases they have executed. There is also a tab for Requirements where the test cases can be linked.

So, by combining those two together, you will be able to see which test cases are mapped to requirements, and if they have been executed. You will also see the number of passed and failed test cases. It is very easy to use once you know all the features. It barely crashes and recovers gracefully most of the time.

The product, at times, does not recognize objects, especially in web applications. It would be good to have that fixed in the next version. As a work around, you have to use the feature called TBox which allows you to scan complex objects.

I have been using it for more than six months.

No issues encountered.

No issues encountered.

No issues encountered.

The initial setup was hassle free. Although, it would be great if the documentation for the initial set up would include more screenshots and a troubleshooting section.

For our applications, it makes the test cases. So far, we have been quite happy with it. So, we don't have any complaints.

We build the test cases, then we just need run it by one person to get feedback right away. Otherwise, it would require planning with certain testers.

Compared to other tools we have been looking at, you don't have to be a programmer to operate it, though it helps. It also a product that can be used by business people.

• It needs better integration with JIRA.
• I would like a better user interface.

It is stable.

It is scalable.

We are satisfied with the support of Tricentis so far.

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. 

It took time to begin setting up for the first time because it's not a regular setup. It took us a week to set up.

We hired a consultant to figure out all the tools in our company and how they fit in our company before we purchased the solution.

We also evaluated HPE, IBM Rational Functional Tester, and Ranorex. However, for us, Tosca was the perfect choice.

Figure out your requirements and environment.

We had the impression Tosca would be the perfect fit for us. We did a proof of concept test with all our applications, Tosca was able to work with them and drive the proof of concept goal. Finally, we made a decision a year ago to work with Tricentis Tosca. We are quite happy with the product.