Tricentis Tosca Reviews

My primary use cases for Tricentis Tosca include SAP testing, end-to-end testing for web applications, API testing, and data integration testing. I use Tricentis Tosca as a customer, implementing its features in various testing scenarios.

The most useful features of Tricentis Tosca include API scanning, basic web application automation, and data validation capabilities. It is easy to automate tasks, highly flexible, straightforward to learn, and easy to maintain.

We need to automate the manual test cases written by the manual functional testers. We automate those scenarios, which helps the functional testers in the regression run or in the smoke testing. We create scripts in the automation tool that generate data as well. For example, if we need some kind of data in Salesforce or any Dynamics, we run those scripts with the test data and share the data with the BA or the UAT testers. This is how we are using this tool.

Tricentis Tosca is a codeless tool, making it easy for everyone to understand the transition of how to develop scenarios or test cases.

In Tricentis Tosca, analyzing failures is straightforward because every time it fails somewhere, I get the screenshot, which helps me analyze how and why it failed. It has all the modules, including some pre-built ones that can be reused efficiently.

Compared to other code tools such as Selenium, where I used to develop one script in one day, with Tricentis Tosca I can easily develop one script in four hours or three hours, saving four to five hours in a day.

My customers' usual use cases for Tricentis Tosca revolve around test automation for automating testing for web, SAP, Salesforce, databases, and APIs.

The most valuable features of Tricentis Tosca are the modular approach and Vision AI. The modular approach reduces scripting effort by at least fifty percent, which significantly cuts down on the script development time. Reusability is high, resulting in effort reduction. Additionally, the Vision AI feature is really good. The Scan module, reporting, and execution are also highly effective.

I have experience with the automation of software for testing, such as Tosca, Selenium, and others.

We automated the end-to-end process with Selenium, from activation to custom provisioning. I supported the Tosca consultant with Tosca expertise to rebuild the same use case using the Tosca platform.

We're a consulting company. The company bought the licenses for the software, and we're providing consultancy to create a software factory. Some tools have been used for years.

We have manual testing, and we build the same tests using Tosca cross-platform for end-to-end processes. For example, when there's a new portfolio, we push the new offers and do regression tests. 

We also monitor the quality assurance environment for errors when new features are implemented. When there's a project with a new feature, we do the regression part, or if there's a price up, we do automatic testing for efficiency.

It's also the most expensive. You don't do the coding or implementation part because they're hoping to get more users to acquire more licenses. Currently, two people do the coding, and we provide assistance to show the flow for implementation in Tosca, copying what we implemented using Selenium, how we create test data, and the entire end-to-end process. I don't know the detailed features of Tosca. I only see remotely what the other person implementing it does, and we do step-by-step babysitting to migrate the automation from one platform to another.

I am doing automation for different applications such as SAP, Worksoft, LogJ, Salesforce, and other desktop, web, and other applications.

The scriptless automation tool is one of the important features. It allows for drag-and-drop functionality and demo automation in SAP-based applications, which can be challenging with other automation tools. Model-based automation is another good feature, allowing similar models to work by changing the engine. The integration capabilities with QTES tools, CSE tools, or JIT also improved a lot over the years.

From Tricentis, I have used Tosca for test automation and qTest for test management.

I use the solution in my company since many clients use SAP. Most of the clients have some SAP solutions with Fiori and SAP ECC. The last use case we did was on a client, so we are implementing Tosca for automated test cases and for rollouts in different countries. We had about 50,000 automated test cases.

The most valuable feature of the solution stems from the fact that it offers technology coverage because you can automate any technology, like in the mainframe, applications, client applications, or Word documents. I would say that we can automate the entire flow for endpoints where we work with such tools.

It's a very user-friendly tool. Anyone can learn it easily without needing any coding skills. You can just watch the demos or videos, and then start using it because it's very straightforward and user-friendly.

Data management is simple. You can manage and use your data and test cases. Resiliency is a key feature.

There is also version control. 

Use cases for Tricentis Tosca include applications that interact with multiple platforms, such as SAP, web applications, and mobile applications. For instance, a typical use case might involve an application that connects to SAP, a web application, and a native mobile application. The workflow may then return to the server and interact with web and SAP systems.

Tosca is coupled with SAP ECC and the SAP application itself.