What is your primary use case for Tricentis Tosca?

We use Tricentis Tosca to test workflows.

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.

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.

I use the solution for functional and automation testing.

We use the product primarily for functional testing. It is highly effective for mainframe-related test cases and other traditional applications. Our environment includes many mainframe tools and applications that are automated using Tosca.

I use the solution for software validation.

We are using it daily as the best automation solution.

As a codeless automation tool, the product offers a user-friendly experience without requiring extensive coding knowledge. Users can easily handle various applications, including web applications, SAP applications, Windows applications, and even Salesforce applications, without manual coding. This ease of implementation and time-saving feature distinguishes it from other products. The tool provides a smooth transition from Selenium and other tools, allowing users to develop frameworks for different functional workflows. The ease of downloading and activating the tool, emphasizing productivity and time-saving features, makes it a valuable choice. We can handle multiple execution and test cases.

Tosca offers end-to-end automation capabilities. It has strong features for managing test data, code, and locators. Additionally, it includes a record and playback feature for ease of use. 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.

Our customers use it for low-code, no-code testing, near-field communication (NFC) testing, Salesforce testing, and UI testing.

We use the solution in our company for all kinds of automation, so we cannot specify anything.

We use the product for web and API automation.

Tricentis Tosca has many use cases. Currently, we are using it for Salesforce testing. The solution can also be used for work safety testing and for API testing.

We utilize Tricentis Tosca to reduce our release cycle timing for our SAP releases. We have at least one release every quarter. We also use it for automation.

Our primary use case of Tosca is for the automation of web-based applications. We currently have five clients who have deployed this solution. I am the practice head and we have good capabilities in this tool.

We primarily use the solution for automation testing.

We use Tricentis Tosca for a workflow system.

We are using Tricentis Tosca for test automation.

Tool consolidation - We had different tools like UFT, worksoft, provar and then selenium which was making the automation portfolio very large. We needed skilled automation engineers on each of the tools to do maintenance and execution. 

Learning curve - With TOSCA the learning curve was lesser so we could train our existing manual testers on Tosca to script, execute and maintain scripts instead of depending on additional team members to support automation. 

We use Tricentis Tosca for test automation.

We use Tosca for writing the test cases. It can do multiple things, like linking test cases to requirements and generating custom reports for the queue test. Tosca is deployed on-premises, and more than 500 people are using here. I've also worked with Tosca VI, which is part of our PTL automation. When did a POC for Tosca VI where the Tricentis team came to India and designed a solution for our requirements.

We use it to automate testing. In terms of the version, we're up to date. We're on the latest version.

My primary use case for Tricentis Tosca is SAP testing.

We use Tricentis Tosca for Salesforce automation.

We were not able to automate the mainframe or maybe the backend test cases to other tools. That is why we switched to Tosca. Tosca can give us the UI plus the backend mainframe and API testing within one tool. That is why we need Tosca.

Tricentis Tosca is used to test our in-house products. We have developers for Google and other web applications for our internal use, but that product is developed by outsourced developers, that needs to be tested.

We use Tricentis Tosca mostly for API endpoints. We are testing the integration with systems.

Tosca has been used for automated testing with our business process management tool, known as Athium, as well as our GRC tool, Archer. It assists us in putting together automated testing for those two platforms in order to manage test coverage and do it in an automated manner as opposed to how it was done manually.

We use Tosca to automate progressive and regressive tests. About 60 people in my company are currently using it.

We use Tricentis Tosca for testing.

Automating SAP and NON SAP applications

We have been using this solution in my organization. There are several clients who have come back to us asking for different automation tools and our views on which automation tools can be used in their respective projects. We have been evaluating for these clients. The evaluations we were doing, was for our client but done within the organization only.

We are using this product for web UI testing, SAP, and API testing.

We use this product for testing and trying to make solutions work.

We are using it for user names and login passwords. We are using model-based techniques where they have already entered IDs. Based on the ID, we can create the object, test case, test folder, and test types. If I want to create a registration for five countries, I will create complete test cases and use the same data. There is no need to create different data or test cases for that. I can use the same data for different countries by using or passing the object from my object type. In my previous company, I worked on two different projects. One was for the banking domain, and the other one was for the telecom domain. In both projects, I worked with web-based applications plus Windows-based applications by using Tricentis Tosca. I designed around 55 to 60 case designs in one project. I also worked on the test case design, maintenance, execution, delivery, and reporting. I wrote user stories and created some examples for test case stories.

We are primarily using this product as an automation tool, for regression, and as a revision tool.

We primarily use the solution for testing. The company's businesses are tax-free payments. We're testing the company applications around the aspects of its tax-free payment systems.

Our primary use case is UI-based regression tests on Microsoft Windows.

We primarily use it as an MBT, a model-based automation tool.

It's primarily used for automation. We're a pretty complex environment. We have hundreds and hundreds, if not thousands, of applications. We have more than 200 Agile teams which are doing builds across five big locations in the US.

We use it for test automation and manual tests, and we use it as our central repository for all test cases. Our test cases focus on front end testing and back-end testing. Tosca BI is what we use for back-end testing. We also have built out RPA processes that run in Tosca in conjunction with DEX.

We use this solution for risk-based testing in conjunction with test optimization and test automation. Our testing landscape ranges from web applications to mobile applications to mainframe to PDF. The tool takes care of most of the testing requirements with relatively minimal effort.

Primarily test automation for webshops based on PHP code. It was satisfying as long as the GUI did not change permanently.

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 are using it for end-to-end automation. The performance is good. It's just that it doesn't support applications on the Mac. But overall it is good.

Mixed environment having web and desktop applications, integrating with each other and over an API Gateway.