Tricentis Tosca Reviews

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.

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.

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.

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.

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.

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.

I cannot recall the exact licensing terms of the price of the product.

I did do a proper comparative analysis of other solutions with regards to pricing. 

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.

We use Tricentis Tosca for overall test management.

Tricentis Tosca is well integrated with other products like Jira. It's also relatively easy to use and doesn't need experience or a specific skill set.

Tricentis Tosca’s technical support could be improved.

I have been using Tricentis Tosca for about eighteen months.

I rate Tricentis Tosca a nine out of ten for stability. We've had no issues so far with Tricentis Tosca's stability.

I rate Tricentis Tosca an eight or nine out of ten for scalability. Around five users in the test automation space are using Tricentis Tosca in our organization.

A couple of times, we approached Tricentis Tosca's technical support and got the answers to our questions.

Neutral

Tricentis Tosca was already configured and running. The installation took 10 to 15 minutes, and access and setup were very, very quick.

We did not need any assistance for the solution's implementation. It could be done without any help.

Tricentis Tosca is not expensive at all. Tricentis Tosca's licensing cost seems to be in line with other products. We're currently using a per-user license because there are only four or five users. I rate Tricentis Tosca an eight out of ten for pricing.

I use the latest version of Tricentis Tosca. The solution does not require any maintenance because it is all done automatically by the vendor.

I've not found any issues with Tricentis Tosca, and I would recommend it to other users.

Overall, I rate Tricentis Tosca an eight out of ten.

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.

The solution is very user-friendly and the low code automation is great and very helpful.

It was very difficult to get information about licensing costs. None of that information is readily available. For customers with a smaller budget, it would be helpful if Tricentis could offer options for smaller organizations to be able to use the tool. We've also found that customer support is lacking. 

We've been testing the trial version of this solution for the past several months. 

The solution is stable. 

The solution is scalable. 

Reaching out to customer support is challenging and they could improve on that. 

Neutral

We previously used other tools but our clients switched to Tricentis because of its ease of use.

The initial setup was easy.

This is an expensive solution. 

I rate this solution eight out of 10. 

We use Tricentis Tosca for test automation.

The most valuable feature of Tricentis Tosca is the Tosca Commander. Functionality is another thing I find most valuable in the solution.

What needs to be improved in Tricentis Tosca is its centralized repository mechanism because it's not as flexible. The repository in the solution where you store the data and the script for test automation is quite an old-fashioned mechanism that could be improved.

An additional feature I'd like to see in the next release of Tricentis Tosca is a distributed repository mechanism because it's required in the current installation for my company.

We have a contract with Tricentis Tosca, and we've been using the solution for six years now. We're using the latest version, which is version 14 because there was this bug called the Log4j.

Tricentis Tosca is a pretty stable solution.

In terms of scalability, that's a challenge in Tricentis Tosca. Scaling the solution is quite difficult because it uses only Windows environments, so it's not a good solution for scaling up. Right now, we rely on Windows, but we are moving to the cloud, so scaling Tricentis Tosca would be difficult for us.

The technical support for Tricentis Tosca isn't quick, but it's useful.

The initial setup for Tricentis Tosca was pretty straightforward.

Initially, for the deployment of Tricentis Tosca, we used a consultancy company, but now we do its deployment in-house.

In terms of the licensing costs for Tricentis Tosca, we are spending more or less $70,000 per year. We have a very complex mechanism because there are some business users and some BI users, so the licensing structure is not simple, but support is included.

My company is using Tricentis Tosca and is an end-user of the solution.

With the Tricentis Tosca installation that my company has, one person is enough for maintenance.

My advice to others looking into implementing Tricentis Tosca is to limit it. I would use it only for specific test automation requirements, and I wouldn't use it for other purposes because it's a very expensive solution.

My rating for Tricentis Tosca is seven out of ten.

My primary use case for Tricentis Tosca is SAP testing.

I'm using Tricentis Tosca as part of test automation, so it reduces the test execution time, and this has improved our organization. This is the main advantage of the tool, compared to doing it manually.

All the features available now in Tricentis Tosca are valuable.

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. OpenText is a company which provides multiple applications.

There's also an issue with the support for Tricentis Tosca. If they don't provide support within a faster timeframe, then you will wait for the solution, and you'll lose, e.g. whatever you're gaining from the tool, you'll lose, because of the delayed support.

Tricentis Tosca also needs some improvement, and this is why my rating for it is only eight out of ten, e.g. it needs to have more compatibility to be able to take advantage of its multiple features.

The tool also supports on-premises deployment only, and it needs to elevate to cloud deployment. It should be easily accessible by anyone, and this is currently not the case. Other competitor tools, or most of the competitor tools, have moved to cloud, except Tricentis Tosca.

The licensing cost for the tool also needs improvement.

If these changes were to be made, then I could give Tricentis Tosca the perfect score: 10 out of 10.

I've been using Tricentis Tosca for six years.

The stability and reliability of Tricentis Tosca is just 60% for me.

We were able to contact technical support for Tricentis Tosca, and they gave us a delayed response. In order to get our problem solved, we had to wait for one month.

The initial setup for Tricentis Tosca was a mix of both straightforward and complex. If you are using just one component, the setup was straightforward, if you wanted to integrate the tool with the multiple components, then the setup becomes complex.

The installation was standard in terms of how long it took to complete, e.g. one week. If there was integration, it could be completed in three weeks.

I've seen a return on investment from the tool, but only when it was used long term, e.g. in more than three years time.

The licensing cost for Tricentis Tosca is expensive. It has multiple features, but to use all of its features you have to pay for additional licenses.

Tricentis Tosca is a testing tool, so we can implement it in any software projects.

The tool is only applicable for on-premises deployment. Currently, it's not possible to deploy it via public or private cloud.

I'm using version 15 of Tricentis Tosca.

I did the deployment of the tool myself, and didn't use an integrator, reseller, or consultant. One person can deploy Tricentis Tosca.

We have 1000+ people in our environment who are using the tool.

Product-wise, I'm rating Tricentis Tosca eight out of ten. Service or support-wise, my rating for it is six out of ten.

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.

Tricentis Tosca has helped organizations process tasks faster and more efficiently.

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.

I have been using Tricentis Tosca for approximately six years.

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.

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.

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.

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.

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.

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.

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.

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.

I have evaluated other tools.

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.

We are using the solution on cloud. We have the updated version. Each time a new version is released, we already have it. I'm not sure what version we're on right now.

We have teams of around 5 to 10 people for different projects that are using this tool.

It's been very helpful to have connectivity with mobile. The tool also identifies some of the actual changes from the recordings on the actual testing suite. That is something that I really like.

The technology stack that they have now is bigger than when it started. That gives us more flexibility on aligning to one single tool to get automation from different technologies in one test scenario. Instead of dividing them and splitting them into different parts, we can go from end to end with this tool.

I would like to see more implementation of AI on the self-healing aspect. That would be like the next step.

I have been using Tricentis for a couple of years.

Technical support is fine. We get a very quick response from them.

We have this as a service, so the initial setup is not that complex. It's already there, and we can plug in and start doing our automation. But last year, we started with a project from scratch, and we needed some support from Tricentis itself. It wasn't complex, but it required some time to get the tool to the point where we could start using it. It took about four weeks.

There is an annual cost for Tricentis.

I would rate this solution 9 out of 10. 

Something that people should probably be looking at is how technical their team is and whether or not they can do coding. If they are more on the business side where they know all the different flows of the business cases or scenarios, that would be a very good way to use the tool because technical expertise is not required. You should have a couple of resources, but it's not necessary to have  high technical skills.

We use Tricentis Tosca for Salesforce automation.

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.

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.

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.

I have been using Tricentis Tosca for approximately two years.

Tricentis Tosca is very stable if you compare it to Selenium or UFT.

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.

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. 

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.

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.

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.

Tricentis Tosca is an expensive tool and the licensing is not simple.

We have evaluated the Copado Robotic tool.

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.