Automating SAP and NON SAP applications
SME (Subject Matter Expert) at Maersk
Easy to Automate and maintain test scripts
Pros and Cons
- "It is easy to maintain and easy to automate. No coding skills are required to automate. It is also easy in terms of transferring knowledge and skills. Many of my team members shifted over the past one and a half years, and there was no big issue with respect to knowledge sharing. It is a good tool that enables me to re-automate my scripts and update my scripts as quickly as possible. Looking at the amount of rework and maintenance activity that we had done for our scripts, it might have been a nightmare with some other scripting tool."
- "They can make it more stable. I have used this tool for SAP applications. They have an alliance with SAP, and it mostly worked fine, but there were a few glitches. However, we got the required support from the Tricentis team. They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack."
What is our primary use case?
How has it helped my organization?
Reduced Integration testing time effectively from 2 weeks to 1 day for CRM application.
What is most valuable?
With code free automation concept, it's easy to automate and maintain test scripts. Many of my team members shifted over the past two years, and upskilling and knowledge transition was never a problem.
In today's agile and cloud world when solution and functionality are not stable, automation scripts' maintenance was not a big issue. Looking at the amount of rework and maintenance activity that we had done for our scripts, it might have been a nightmare with some other scripting tool.
What needs improvement?
They can make it more stable. I have used this tool for SAP applications. Tricentis's alliance with SAP mostly worked fine, but there were very few glitches. However, we got the required support from the Tricentis team.
They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack.
Buyer's Guide
Tricentis Tosca
February 2025

Learn what your peers think about Tricentis Tosca. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
838,713 professionals have used our research since 2012.
For how long have I used the solution?
I have used this solution for more than one and a half years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
I scaled it up a few months ago, and it was not a smooth process.
Which solution did I use previously and why did I switch?
I have worked on QTP/UFT and SAP TAO for SAP automation. Considering no-code automation, easy maintenance, and integration capabilities with 150 + applications, I selected TOSCA for an automation solution.
How was the initial setup?
Its initial setup is not very complex and needs the required skills/knowledge. It also depends on the environment. It is good to have a TOSCA expert in your team to support integration activities.
What about the implementation team?
We engaged the SI partner for Tosca set up and automation.
What other advice do I have?
We did not fully utilize its integration with the test management tool, but it was working fine.
My recommendation would be to go through Tricentis documentation and the best practices that they are proposing. Wherever required, set up a knowledge-sharing session with Tricentis.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Affordable with helpful support and a simple interface
Pros and Cons
- "It's stable and reliable."
- "In Tosca, I see that there are no user guides."
What is our primary use case?
We have used the product for web application automation and SAP functional automation, as well as for Microsoft Dynamics 365 process automation.
What is most valuable?
There is a specific feature in Tricentis Tosca called Vision AI. What it does is basically it'll capture the entire screen, and you can automate anything that can be viewed on our screen. For example, if you are trying to access an application like Teams, so if you want to select any user and call him, you can do that. Anything that is on a screen, you can automate using that Vision AI tool.
The interface is pretty simple, and it's user-friendly, so people with minimal knowledge also can start using the Tosca tool. The widgets and the invoicing are also user-friendly.
It's stable and reliable.
The solution can scale.
Support is helpful.
Pricing is affordable.
What needs improvement?
In Tosca, I see that there are no user guides. So basically, if you want to automate something, you have to really do some research and then start doing it. Having documentation would be helpful, and that is something that needs to be provided, maybe as a jump start to getting going with the product.
There are certain engines that are available that will identify the objects. Yet, there are some engines that are not available, so we need to customize them.
The setup can take a while as the licensing is confusing.
The response time for support can be slow.
For how long have I used the solution?
I've been using the solution for around two or three years.
What do I think about the stability of the solution?
The stability is excellent. I would rate it nine out of ten.
What do I think about the scalability of the solution?
We have a team of 250 people on the solution right now. We have five active licenses on five servers. We have mostly testers on the product.
It is a scalable solution and a powerful tool. I'd rate scalability eight out of ten.
We likely will increase usage in the future.
How are customer service and support?
There is a lack of a knowledge base, and the time it takes for them to respond is a bit slow. While there is a delay in response, their help is quite good.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I've also used Micro Focus and Selenium.
How was the initial setup?
I'd rate the initial setup around six out of ten in terms of ease of deployment. The initial setup was difficult. However, we took support help from the Tosca team, and then we tried to resolve the issues.
The only issue really is the licensing issue. You need to activate the license and for activating the license, and there is no specific straightforward way to do it. You need to connect to the Tricentis support team, and then you need to get an activation link, followed by their code and all that. It's a challenge.
For deployment, if you have the activation link, it'll be done immediately, instantly, maybe in hours. Otherwise, if you do not have the activation link, then it might take days since you need to connect with support.
What was our ROI?
Most clients I come across prefer open-source solutions and may move towards Selenium to keep the tool cost down. However, if we are using commercial tools like this one, it will take two to three years to realize an ROI.
What's my experience with pricing, setup cost, and licensing?
The pricing is good. I'd rate it eight out of ten in terms of affordability.
What other advice do I have?
We are partners.
I'm working with the latest version of the solution.
I would recommend the solution since the tool is user-friendly and easy to use. It comes with a lot of features, and it's a very powerful tool. I would definitely recommend it compared to other tools.
I'd rate it nine out of ten overall.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Tricentis Tosca
February 2025

Learn what your peers think about Tricentis Tosca. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
838,713 professionals have used our research since 2012.
Senior Technical Engineer at Expleogroup
User-friendly, easy to learn, and doesn't require any coding
Pros and Cons
- "The item that is different from all the other tools is that it's module based."
- "It can be quite expensive."
What is our primary use case?
We primarily use the solution for automation testing.
What is most valuable?
The item that is different from all the other tools is that it's module based. This is the thing that I like about Tosca. It means there is no hassle in coding.
What needs improvement?
Every tool has a disadvantage. There are some technologies that are not scanned, for example.
The product needs more technology coverage when scanning modules as not all the modules can be scanned and we have to check for workarounds. We have to overcome the fact that not every technology can be scanned using the module scanner.
It can be quite expensive.
The product does not have an open-source option.
For how long have I used the solution?
I've used the solution for more than five years.
What do I think about the stability of the solution?
The stability is okay. I'd rate it seven out of ten in terms of reliability. Sometimes I do face issues around stability, however, most of the time, it is fine.
What do I think about the scalability of the solution?
The scalability is pretty good. I would rate it seven out of ten in terms of how easy it would be to expand.
We have more than eight people using this solution in our organization. It could be a bit more. We do have a client on it as well, and we are working with them.
How are customer service and support?
Technical support is extremely good. They are helpful and responsive, and we've been more than satisfied with the level of support they provide. They are the best.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I did use another solution and used a combination of Tosca and UFT. That was five years ago, and the Tosca technology was a bit different. We were not able to scan the system attributes, for example, using Tosca back then. I introduced another automation tool to open it and run the script and then get back to the original script. It was like a work-around and, at the time, it was successful.
How was the initial setup?
The process for implementation is pretty normal and pretty straightforward. I would rate it eight out of ten overall in terms of ease of deployment. I'm just upgrading it, and it is not hard.
How long it takes to deploy depends on the project scale. For the big project, I it would take us two days. The time it takes depends on the VDIs, the number of VDIs, and how they will be scheduled for deployment.
What about the implementation team?
We had a consultant help deploy the solution for us.
What's my experience with pricing, setup cost, and licensing?
The cost is high for this solution. It is one of the highest in the market. That said, most big companies go for licensed automation applications in general due to security. It's not an open-source product. Big companies do prefer the licensed tool over free options.
What other advice do I have?
Our company is partnered with Tricentis.
We're using the latest version of the solution.
I'd recommend the solution to others. It's user-friendly, easy to learn, and doesn't require any coding. New users, however, must take some lessons before starting with it. Most of the time, they might have colleagues to transfer knowledge and that makes things simpler. Still, it's really easy.
I would rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Sr Test Automation Architect at a tech services company with 501-1,000 employees
Efficient operations, continuous improvements, and robust features
Pros and Cons
- "The most valuable feature of Tricentis Tosca is it is a completely scriptless automation tool, which I liked a lot. They keep on continuously improving their tools, wherever we are facing any challenges they are able to provide a solution for it. It is easy to learn, everyone can easily read and understand what is happening with the scripts. Any business user or function tester can use the tool efficiently. This is a complete solution package."
- "Tricentis Tosca could improve on its mobile automation solution."
What is our primary use case?
We use Tricentis Tosca for end-to-end automation. We have various types of applications that we have to automate. For example, we automate Salesforce, SAP, web-based applications, desktops, mainframes, APIs, and database automation.
We use Tricentis Tosca on-premise and in a private cloud.
How has it helped my organization?
Tricentis Tosca has helped organizations process tasks faster and more efficiently.
What is most valuable?
The most valuable feature of Tricentis Tosca is it is a completely scriptless automation tool, which I liked a lot. They keep on continuously improving their tools, wherever we are facing any challenges they are able to provide a solution for it. It is easy to learn, everyone can easily read and understand what is happening with the scripts. Any business user or function tester can use the tool efficiently. This is a complete solution package.
What needs improvement?
Tricentis Tosca could improve on its mobile automation solution.
For how long have I used the solution?
I have been using Tricentis Tosca for approximately six years.
What do I think about the stability of the solution?
The performance of Tricentis Tosca is very good. They have a feature called model-based test automation, which is highly stable and they are improving the solution in very efficient ways. For example, if there is a complete change in the use of the application, such as it was initially implemented in SAP and later on moved into a Java-based application, we can simply utilize the same models. Tricentis Tosca is completely model-based which is very robust.
What do I think about the scalability of the solution?
Tricentis Tosca, it is very scalable. We are using it for end-to-end automation where we are working on completely different types of applications across different technologies. Tricentis Tosca supports more than 160 technologies as of 2018. It supports the majority of the applications generally available outside. You can directly start automating those applications and tools. It is can be easily scaled. We can execute test cases and we are able to automate very well. We are receiving more than 90 percent of coverage with the out-of-the-box Tricentis Tosca.
We have more than 100 users who are utilizing this particular tool. We worked with customers where there are more than 200 licenses, which have started using it. There are different types of licenses and the users are different. We started using this tool for various projects in our application where there are data developers and automation testers. The client started utilizing those test cases for execution.
Tricentis Tosca is the leading solution in the market. They have some competition, such as Selenium and Worksoft Certify. However, I do not find Selenium to be much of a competitor to Tricentis Tosca. Tricentis are investors in Selenium. The Tricentis team's main focus is not on their test applications but focuses on end-to-end automation. It is trying to convey itself as a complete package of test automation where it can perform functional testing automation from a single tool. We see Tricentis Tosca as a complete package solution.
How are customer service and support?
The technical support of Tricentis Tosca is very good. There was a dedicated team of people who were available in the chat window, where we can directly chat within 24 hours a day seven days a week. However, that is if we purchased their dedicated support for them. If not, we have a community of people who are implementing Tricentis Tosca, and there are plenty of practitioners who are part of this community. They always provide the solutions for whatever issue that anyone would be facing.
Which solution did I use previously and why did I switch?
I have used many other solutions, such as Selenium and Worksoft Certify.
We used to use WorkSoft Certify as a solution, then we moved to Tricentis Tosca recently. The reason we switched was the slowness of the automation scripts and some of the areas, such as a drag and drop issue we had where we cannot drag and drop in WorkSoft Certify. We were able to do this with other automation tools. Our teams started switching to Tricentis Tosca rapidly because the exhibition time is a lot faster and more efficient compared to other automation tools. They can directly jump into automation.
Another major reason why the customers are switching to Tricentis Tosca is that the customer can read and understand what is happening in the script, which is not the case with other automation tools, such as Selenium. You need a developer or automation tester to explain what is happening in the script, and you need to provide some comments or explanations. Whatever automation was done in Tricentis Tosca, the customer themselves can read and understand what is happening in the script. This was a good selling point.
How was the initial setup?
We preparing to do the implementation of Tricentis Tosca we talk to the customers on the different areas for their requirements. We have a lengthy call with them, to be frank, in their specifications are. We have a demo of the tool, that we discuss with the customer about their problems. We find out what are the different applications that they have. We do a mock POC on their applications and we do some tests to understand whether the solution is going to fit their requirement or not.
We look to see if they have any customization requirements or room for customization in their applications. They might require specific customized solutions. Unlike tools, such as Worksoft Certify where we have to go to the vendor to receive custom solutions, we can write our own custom controls in Tricentis Tosca. Where customers are having the knowledge, we can create our own custom solutions. More than 90 percent of it doesn't require any custom solutions because it presents itself to provide patches if they come across any issues or challenges. It's a single solution for most of the customers.
What about the implementation team?
Once the installation is ready in approximately a week's time, we can start with the automation. There is no framework or anything needed for this project tool to start with automation. We only need to ensure that we implemented the best practices in the initial days, and we follow the same practices continually.
The maintenance of the scripts is one of the major challenges in any automation tool, such as Tricentis Tosca. The maintenance is very fast and more efficient in the Tricentis Tosca automation tool. There is a coding language called Tosca coding language, we can search for multiple objects where there is a change. We can update thousands of objects with a single click. Within a single second, we can update thousands of test cases. This is a very useful feature that has been helpful. Dividing the technical properties of the objects and on the logical section where we are working on the objects into different areas. It makes it very easy and efficient to automate or maintain the test cases.
What was our ROI?
There were instances where it used to take a massive amount of time for performing the automation using a certain specific scenario. If a normal tester tries to open the file itself, it takes approximately eight minutes. Later on, we have to go and verify each and every value in that particular Excel and cells, which typically can take two to three weeks of time.
Using automation in Tricentis Tosca, it can be done in a single system in less than 10 minutes, the whole process. This is a substantial ROI for the customers because they were saving a lot of time. Normally for the opening of Excel itself, it takes 10 minutes. I understand the different things that can be done there has been a lot of saving that the customer has voiced. They appreciated the solution and they are utilizing Tricentis Tosca for everything they need automation for, such as EPAs.
What's my experience with pricing, setup cost, and licensing?
We have a license to use Tricentis Tosca on-premise and in the cloud.
The pricing and licensing of Tricentis Tosca were alright. Many customers look for end-to-end enterprise solutions, there were not many challenges with the pricing. However, the customers who are coming from Selenium or similar, feel they're paying a premium for this Tricentis Tosca license. If the right person is there for the implementation of the Tricentis Tosca, then it is one of the best tools in the market.
There are other solutions available in Tricentis Tosca. For example, there is NeoLoad, OSV Orchestrated Service Virtualization, Tosca DI, Tosca Data Integrity, and Flood IO. Additionally, there is a qTest integration that is available and the LiveCompare solution, which was acquired by Tricentis for live compare implementation. These additional services or tools requires some specific customers license. If the customer wants to use them it's a separate license. These addons are not always part of the client's requirements and do not need to be purchased. They can directly start with only a Tricentis Tosca license.
Which other solutions did I evaluate?
I have evaluated other tools.
What other advice do I have?
The major challenges that we face with any automation tool are with respect to whenever there are any modifications. For example, when we are working on a tool, such as Selenium or something which is a script-based automation tool. Whenever there are any changes that have to be done, instead of modifying the existing scripts, we normally tend to recreate the script because it takes less time to create a new script rather than updating the existing script, which might be developed by someone else. To understand where the test case is getting failed. However, this is not an issue in Tricentis Tosca where the major issue of maintenance of the scripts is very easy because we have a Tricentis Tosca coding language where you can update your multiple test cases simultaneously.
There were instances in my past experience where the customers informed us that Tricentis Tosca was not good. They said they were not going to implement it again. One of the most important things to know about the tool is how it works. For example, if we are having a knife, we need to know how to use it. If we don't use it properly, there will be some consequences. However, if you know how to use the knife it can be extremely useful for man things.
For any tool to work more efficiently and properly, we need to know how to use it properly. They are providing the certifications and the solutions for free for anyone who wants to learn and implement it. Normally I recommend people to learn Tricentis Tosca and then start implementing it, rather than jumping into automation, using this tool.
I rate Tricentis Tosca a nine out of ten.
I like Tricentis Tosca a lot compared to other automation tools that I've worked on. That's why I recommended Tricentis Tosca. If I have to choose any tool for automation to automate a specific application, I would choose Tricentis Tosca before other automation tools.
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Senior QA Manager at a retailer with 10,001+ employees
Easy to use with good training but scaling can get tedious
Pros and Cons
- "The mainframe testing and UI automation are the most valuable aspects of the solution."
- "The integration with mobile testing could be useful."
What is our primary use case?
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.
What is most valuable?
The mainframe testing and UI automation are the most valuable aspects of the solution.
Technical support is good.
The solution offers good tutorials.
It's pretty easy to use.
What needs improvement?
The integration with mobile testing could be useful. Currently, they use this Perfecto Mobile as the mobile automation tool. If they could switch to others -such as BrowserStack or other tools - that would be helpful. I have used web UI, the desktop UI, and the API, as well as the mainframe. I haven't seen much from a mobile automation perspective as I haven't used it. I'm not aware if there is mobile automation. However, they really should have this if they don't already.
Scaling can be tedious.
What do I think about the scalability of the solution?
From a scalability standpoint, if you are needing the data from Excel and Excel has lots of records, it may be difficult. I want to try for more records, basically between 5,000 and 10,000 rows reading from Excel. That is a bit of a tedious process. Right now, it doesn't seem very scalable if you want to read the data directly from Excel or any other file.
In Excel, you have to create the tables, rows, columns every time. Then, you have to read from Excel. You have to create a similar table structure in Tosca. It's a tedious process.
We have eight to ten automation engineers using the solution right now.
We do plan to increase usage in the future.
How are customer service and support?
Technical support is good. We get all the information through the call centers and they give us tutorials as well. It's not a problem there. We are satisfied with the level of support we get.
How was the initial setup?
The setup was not done by me. It was done by a separate team. I wouldn't be able to discuss the setup. I installed it on my system, my PCs, and the client. That part was pretty straightforward.
What's my experience with pricing, setup cost, and licensing?
I cannot recall the exact licensing terms of the price of the product.
Which other solutions did I evaluate?
I did do a proper comparative analysis of other solutions with regards to pricing.
What other advice do I have?
I did some certifications on Tosca. I tried to do some POCs as well. I'm using the latest version of the solution, which may be 3.2 or 3.5.
I would advise new users to not go with writing the test cases manually. Try to start automating directly in Tosca, as that would help to save time. If you write manual test cases as well and then we try to automate to Tosca, it takes a lot of time. It's better to jump in right away with the automation-first mindset approach and start writing in Tosca so that you could use it in every execution cycle.
On top of that, if you have a different cycle for business users to do the testing or they are testing at the user acceptance testing, you can give them the test use for Tosca as well. It's pretty easy to use, straightforward and it would save time.
I would rate the solution at a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Test Consultant at a tech vendor with 10,001+ employees
Has a wide range of applications with an easy setup and great stability
Pros and Cons
- "The low code is the best feature."
- "It requires some coding customization that requires expertise."
What is our primary use case?
We use this solution for a lot of their applications. For example, we use GIS map-based applications and develop solutions around them. We also use the technology to draw a polygon and use API for the mobile solution. We use a silver-based application that will soon be obsolete and some cloud-based applications.
What is most valuable?
The low code is the best feature, and clients like it.
What needs improvement?
We are still exploring the solution but would like a capability where the infrastructure has a code that we can verify using Tricentis Tosca. We are examining how to integrate this with the keyboard and our credentials through Tosca. We want to integrate with other solutions for credential repositories, so we don't need to provide a username and password in the solution explicitly. It would be good if it could grab a specific key and utilize it in the task for execution.
Currently, with Tricentis Tosca, we need to install it as an application on our machine, but it would be better if we could assess a solution. It requires some coding customization that requires expertise, so having free services along with the licenses would be good. Some clients have complained that they need to pay for additional services every time they open a ticket.
For how long have I used the solution?
We have hands-on experience with Tricentis Tosca and have completed Tricentis Tosca training because we are an Alliance partner. We utilized it when we completed training on installing the software, ES1 and ES2. We have been trying to purchase this tool for almost two and a half years. Our clients are almost updated on it, and we are about to deploy this solution in our client locations. They will be using version 15.2.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
We have no issues with scalability. We have a solution architect and a few team members who will develop it.
How was the initial setup?
The initial setup was not complex, and there were no hurdles.
What other advice do I have?
I rate this solution an eight out of ten. From a UI perspective, there are no issues, but pricing could be better. Our clients had been asking for this solution for over two years, and pricing was the main reason we didn't have it. I would recommend this solution to other companies if they have the budget.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Senior at a financial services firm with 10,001+ employees
Using exploratory testing, we can send an email to record manual test cases to the business analysts.
Pros and Cons
- "With one click, it will scan all the elements on the screen, so that the user can select the required elements for automation tests."
- "They need to improve on the reports after the execution of automation tests, since all the current organizations are looking for detailed graphical reports."
What is most valuable?
Below are the features that are the most valuable in regards to this product:
- With one click, it will scan all the elements on the screen, so that the user can select the required elements for automation tests.
- Exploratory testing gives an option to record a video, has interactive steps to capture a manual test case flow, and it can be converted to a PDF document with links for the video.
- Using exploratory testing, we can send an email to record manual test cases to the business analysts (BAs) who never need a product to be installed in their machine. The recorded files can be stored on a common server (that needs to be set up separately) or they can send those files to the intended automation team via emails.
- Not much in the way of programming skills is required to use this product.
How has it helped my organization?
Our organization is satisfied with this product on the technical side of it, but our organization was looking for the reporting part of this product since they undergo an auditing process for each year. The reports should be improved for the Tricentis Tosca product.
What needs improvement?
They need to improve on the reports after the execution of automation tests, since all the current organizations are looking for detailed graphical reports.
My previous company uses an application which will create a purchase order for their products, so my company wants to track all the purchase orders and the accounts that have been used for testing. We have set up data and automated tests in Tricentis Tosca. Using the Execution Folder (in Tosca) we are able to execute automated tests which gives detailed information for each run/execution. However, we were expecting a report for each execution like what scenario executed, what data was used (dummy customer accounts) and the resulting purchase order numbers.
Tricentis Tosca is able to export the execution results in Excel/PDF format but our company was expecting customized reports, so I mentioned this as room for improvement.
For how long have I used the solution?
I have worked on this product for six months.
What do I think about the stability of the solution?
There are no issues with the stability part of the product.
What do I think about the scalability of the solution?
There are no issues with the scalability of the product.
How are customer service and technical support?
I would rate the technical support a 9/10, their turnover time is very good.
Which solution did I use previously and why did I switch?
We have used HPE UFT (formerly known as QTP) and Selenium, but some of the critical applications that we needed required different automation tools so we switched to Tricentis Tosca.
How was the initial setup?
The product's setup is pretty much straightforward, no issues in regards to that.
What's my experience with pricing, setup cost, and licensing?
I am not much involved in the pricing and licensing.
Which other solutions did I evaluate?
We explored tools such as HPE QTP/UFT, Selenium, Ranorex and TestComplete but these tools require some specific programming skills to start. Tricentis Tosca doesn’t require any programming skills and it’s a codeless automation.
What other advice do I have?
For a manual tester who wants to become an automation specialist with no programming skills, this is the right tool for the future.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior QA Automation Architect -DevOps and Digital at a computer software company with 10,001+ employees
Smooth automation, beneficial third party solution integration, and highly reliable
Pros and Cons
- "The most valuable features of Tricentis Tosca are the Salesforce scanning. There are two scanning for Salesforce applications. There is Salesforce scanning and normal application scanning. Object identification has been really useful in Tricentis Tosca."
- "The source controls that are in Tricentis Tosca have some problems. For example, if you use Selenium or use Java-based application, it's easy to match code from two developers. However, if you're a developer and going to look at Tricentis Tosca, it's very difficult to use the source control measure."
What is our primary use case?
We use Tricentis Tosca for Salesforce automation.
How has it helped my organization?
Tricentis Tosca has benefited our company by allowing us to onboard testers easily. We have a few developers who develop the code, such as scripts for the team. The manual testing team can execute the code without a problem.
The regression testing time, was five days earlier. For example, in the current project, it took us five days for the release. Since we have used the solution it only takes us two days. It is a savings of three days. It's easy and much more stable. The results we receive are hard to believe.
We have experienced that when we used Selenium, we can have some failures. Tricentis Tosca is much more reliable compared to many of the tools. The reliability and efficiency of our teams have improved a lot from the use of this solution.
What is most valuable?
The most valuable features of Tricentis Tosca are the Salesforce scanning. There are two scanning for Salesforce applications. There is Salesforce scanning and normal application scanning. Object identification has been really useful in Tricentis Tosca.
The API testing has been useful. We can do testing in Postman and we receive good responses. We can import the Postman to Tricentis Tosca and start using it right away. The manual testing to automation can be done smoothly. You get the Postman sponsors from the manual testing team and we can import it to this solution.
There is a source code repository within Tricentis Tosca. There is no need to use GitHub or something else. We can do provisioning and all the switches in Tricentis Tosca. We use qTest as our direct test management tool, and it is integrated with this solution. Once installed it can easily be used and it is very easy to share the objects across the projects, such as if one developer scans all the pages we can share them across all the modules. The modules can be shareable as well. The reusability of some of the features is very good.
Overall the solution is easy to use compared to any other tools, it's very easy to organize and develop. It's simple for new people to have them be onboarded. There's not much coding involved, and the framework is stable.
Tricentis Tosca supports Salesforce Lightning which many other tools will not.
We are using the Tricentis Tosca BI testing module, analytics, and data testing and they have been great.
What needs improvement?
The source controls that are in Tricentis Tosca have some problems. For example, if you use Selenium or use Java-based application, it's easy to match code from two developers. However, if you're a developer and going to look at Tricentis Tosca, it's very difficult to use the source control measure.
If you have any issues with the tool, we had to go to the support system of Tricentis Tosca. We cannot change anything, such as the DLL files. We had to wait for them to deploy the package and it takes time. If I have some tool issue, it takes a month to resolve it, because normally the DLL comes, and then we have to recompile everything and then deploy it. It takes a lot of time.
We use Copado as our CI/CD pipeline and Copado has no integration with Tricentis Tosca. Other solutions can support Copado, such as Jenkins or Areo. We are using a different approach to do the CI/CD operations.
For how long have I used the solution?
I have been using Tricentis Tosca for approximately two years.
What do I think about the stability of the solution?
Tricentis Tosca is very stable if you compare it to Selenium or UFT.
What do I think about the scalability of the solution?
The solution supports a lot of applications and it supports the leading applications. It can scale very well.
We have approximately 80 people using the solution in my organization. However, we are limited by the licensing cost but what we use of the solution we are using it to the maximum.
How are customer service and support?
In Tricentis Tosca we cannot change anything. If we have some issues, we have to go through the support system and receive the support, but the support system is not that efficient. If you have a blocker from the tool side, it takes a long time for a solution. For example, if I'm a developer, we can use GitHub, Aleo, or any other tool for source control.
We can check-in, check-out, deduct the files, review, and again do a review, such as pull a request. However, this is not available in Tricentis Tosca. We had to do reviews offline and we cannot give comments on this solution. For example, if I have a junior developer develop something, there is no way I can promote the code into the route directory. I have to do it all on a manual basis. There is no other review mechanism in the tool and neither does it support, integrate with GitHub or any other repository. We should have code within Tosca itself. There is no other way to take out the code.
The support from Tricentis Tosca needs to be improved. I have not been happy with their support. When I try and contact them I have found it difficult to get through to the first level of support. I then have to go through other communication channels for assistance.
I would rate the support from Tricentis Tosca a two out of five.
Which solution did I use previously and why did I switch?
If you use other solutions, such as Selenium or UFT, but we had issues in identifying objects. We did not have the same issue with Tricentis Tosca.
How was the initial setup?
Tricentis helped with the implementation of Tosca. We are not using the cloud version because of security and compliance issues. It has been difficult. If it is in the cloud version, it is easy. If you're using the in-house on-premise version it's painful because we are supposed to do the deployment. Each build and deployment takes time, but if you use a cloud version, it is now seamlessly working.
We have a separate team to do the implementation, but it was easy for them. It took approximately two, to three weeks. Many things have to be done first inside, such as the DevOps and management, they need to first get the build. We compare, are we deploy it in our QA server, then we deployed the production server for their process. I am not sure of the exact breakdown of the deployment process time. The full process took a couple of months to set it up.
What about the implementation team?
Initially, we used a consultant to do the implementation.
Tricentis Tosca has minimal maintenance, it is a setup-and-go type solution. The only thing we had to do is create the workspace. We use the two ways to do it, single-user workspace or multi-user space. We have now moved from single to multi-user. That takes some time to do because of the slicing and dicing of the workspace that we have to do. We have to be careful about the planning of Tricentis Tosca.
The maintenance is straightforward. Once you install it, it's great. There is no need to have any updates everything is controlled to the centralized agent system. If we are to receive an upgrade, it's all handled through our IT team. They update all the systems, to whatever needs changing which is done through a backend system. There is no need to do individual updates.
What's my experience with pricing, setup cost, and licensing?
Tricentis Tosca is an expensive tool and the licensing is not simple.
Which other solutions did I evaluate?
We have evaluated the Copado Robotic tool.
What other advice do I have?
From experience from using UFT, if they just compare UFT to Tricentis Tosca, I think Tricentis Tosca is a great tool compared to any other tool I have experienced.
UFT is much more heavy compared to Tricentis Tosca which is lightweight and easy to learn and to work with. The stability of the Tricentis Tosca application is great. There is no scripting required in Tricentis Tosca as there is in UFT. However, there is more web scripting. You can do scripting separately and if you're going for a commercial tool Tricentis Tosca is the one to choose.
I rate Tricentis Tosca an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free Tricentis Tosca Report and get advice and tips from experienced pros
sharing their opinions.
Updated: February 2025
Product Categories
Functional Testing Tools Mobile App Testing Tools Regression Testing Tools API Testing Tools Test Automation ToolsPopular Comparisons
OpenText UFT One
BrowserStack
SmartBear TestComplete
Perfecto
Selenium HQ
Sauce Labs
BlazeMeter
Worksoft Certify
LambdaTest
Ranorex Studio
ReadyAPI Test
ReadyAPI
OpenText UFT Developer
Parasoft SOAtest
Buyer's Guide
Download our free Tricentis Tosca Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Tosca Testsuite Version 10.0
- Cost of TOSCA Testsuite?
- Is anyone using Tosca for Non Functional Testing?
- Does anyone know which CI/CD tools integrate with Tricentis Tosca?
- Looking for documents about TOSCA Testsuite
- What are the benefits of Tosca?
- Is Panaya Test Dynamix better than Tricentis Tosca?
- Tosca Testsuite with Selenium WebDriver
- How does Micro Focus UFT One compare to Tricentis Tosca?
- Do we require a separate license for DEX in Tosca?