Tricentis Tosca Reviews

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.

There are two main use cases of Tosca. It is typically used for test automation, which is its main use case. Another use case is the test case design, which is around modeling an application from a business perspective. 

The automation engine is very strong, and it is very competitive in the market in terms of features. They develop a lot of features. 

It is very expensive as compared to other tools that we have in the market. Its price is the main challenge because of which it is sometimes hard to sell Tosca because customers don't have that kind of budget.

Their license management should be improved. One of our customers is a global customer. They want to use one licensed server and then split the licenses based on the different users of the different business units, but currently, there is only one license server that everybody can access. There is no control, and that's why sometimes congestion can happen. It is good for Tosca because they can say, "Hey, your license count is overrun. So, you get more licenses or buy more licenses," but from a customer's point of view, this is really bad because they don't know exactly what usage is happening against each business unit because they can't group them. That's a big problem. So, for each group, they have to clear different license servers in different VMs. That's definitely a key area of improvement and a major challenge I have faced. They could also provide short-term licenses, such as three-month or four-month consumption licenses.

In terms of the overall architecture, we need to have something light weighted rather than so heavy. If we have something light-weighted, it would definitely be easily adaptable for any customer. In terms of containerization, it is very hard to properly containerize Tosca. They can think around the architecture and simplify things, but to be fair to them, the product has grown organically, and it has always grown based on feature requests. Everybody has jumped in and provided feedback to them to develop new features every now and then. They always have had a busy pipeline, which I understand, but it has been a long need from a customer point of view to have a simplified architecture. They need to simplify their architecture, which they seem to be doing.

Reporting has been the biggest challenge for a long time. There are quite a lot of third-party products, but there is no proper integration. Based on what I remember when I last spoke to them, they are working on a cloud platform, and they want to re-platform everything. I'm guessing they are addressing these issues in that platform.

I've tried Vision AI that they have created, but it isn't there yet. They have oversold it. It looks promising, and in the next few years, hopefully, it will become very good.

Their support can also be improved.

I have been using this solution for almost eight years.

It seems stable. It has improved over the years. I've worked with it from version 9.1 to version 15. Based on what I've seen in the past, its performance is much better now.

It is scalable because there is no coding, but from an architecture and infrastructure perspective, it is very hard. So, scalability is a problem because the architecture is heavy.

Their support is okay. If you get the right people, then it is awesome because they will jump into a call and show you what needs to be done. They will help you, but getting that right person is a big challenge. 

When you log a ticket, you get a response, which is a very standard response, and they don't follow up with you. If someone is not following up, that ticket stays there for long. So, the problem is around the management of the people there. I have seen support from other companies as well, and Tricentis can improve from the support perspective.

It is simple. The only challenge is the high infrastructure cost associated with it. Sometimes people underestimate it. It's not a true SaaS solution. Based on the discussions I had, they were moving towards SaaS, and that's the future, but at this point, it's a very heavy solution that is dependent on the on-premise infrastructure, but the installation is easy. You can do it via GUI and you can do it unattended through the command line. So, installation-wise, I haven't faced many issues. They are more around the configurations and the actual infrastructure. 

We are one of the top partners of Tricentis, and we do the implementation. 

In terms of maintenance, Tosca is easier to maintain than other solutions such as Selenium and any open-source tool. The only challenge is the infrastructure cost. You have to have that infrastructure always up and running. If you are setting up this infrastructure on the cloud, utilization becomes a big challenge, specifically when you want to run multiple test cases on multiple machines. You have to set up all these agent machines, which is also a problem with UiPath. These are good tools, but they are not good in terms of future infrastructure cloud readiness. If I want to install things, there should be flexibility for ramping down and up based on the demand. This is something that none of these tools have at this point. Selenium probably has this because it is open-source, and you can create your own framework on top of it to add those features, but with Tosca and UiPath, because these technologies and features are controlled by the company, you can't add those features, and if you don't have those features, it becomes a big dependency and a problem.

Tosca is expensive. I don't see small and medium customers going for it. It's always large enterprises that have a big pocket. It is very expensive as compared to the other tools that we have in the market. They should reduce the price by half, and if they do that, they would do better business. From the competition perspective, other solutions are at a pretty similar level. UiPath is also very expensive. 

One thing that I always wanted was a short-term consumption license. With Tricentis, the biggest challenge is that you have to go for a minimum of one year license, and they also try to sell you a three-year license. It would be good if people can get a three-month or four-month consumption license. It should be on a monthly basis versus on a yearly basis. In today's world, the DevOps teams are decentralized, and the budget is decentralized. A project manager doesn't have a budget for the entire enterprise. He only has the budget for his project or for two or three testers. They need to deliver certain features with two or three testers. If they have to use Tricentis Tosca, it is very hard because Tricentis will force you to get a one-year license because, for them, recurring revenue is important. Even though they claim to be a continuous testing leader, in the real DevOps world, they have struggled to sell because of this factor. When the teams are small, they need flexibility, and if you don't give flexibility around license, it is very hard.

In terms of licensing, typically, we have concurrent users. You buy the license, and that license can be installed on a server and anybody can use it. If you use it, that license gets checked out by your name, and nobody else would be able to use it. It is based on concurrent users, rather than named users, which is good. 

Nowadays, everybody is trying to copy Tricentis Tosca because it is a leader in this space. It is the leader as per Gartner, Forrester, and PeerSpot. Every tool has its pros and cons. One particular product that I liked was Provar, which is specifically for Salesforce. They really went into the code to track any changes. Apart from that, open-source solutions are its biggest competitors. I've seen a lot of open-source frameworks that are better than Tosca and have the flexibility on the containerization side and the reporting side, but from the commercial tool perspective, Tosca is a leader in every aspect. I haven't seen any other tool that has a better capability than Tosca. The automation engine is pretty strong in Tosca.

If you have a manual testing background, it is much easier to adapt to Tosca, but if you're coming from a coding background, you will have to unlearn and think from a manual tester's perspective and work with Tosca. There is a learning curve. So, you need to go through that learning curve, and you should be ready for that. It isn't very complicated, but you definitely need to spend some time. You would need at least two to three months. Their training is not that great. It gives you a basic idea, but it doesn't give you project-related ideas. You really need to work on real-time projects to actually understand the value of the tool.

I would rate it an eight out of 10. There are certain things that they can improve. Apart from those, it is pretty good.

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.

We needed a testing tool that could be used for automating SAP, so that was our use case for Tricentis Tosca, and amongst the candidates we tested, the solution suited us well.

To me, what stands out the most about Tricentis Tosca is that even if I'm not a technical tester, I could pick up on how to use it very quickly because of the mechanisms of the tool, for example, its scanning mechanism. I'm not so technical, but I'm able to maneuver through Tricentis Tosca and derive capability. It's a user-friendly tool. It's not very complex.

In terms of areas for improvement, Tricentis has a variety of tools, even its test management tool called qTest. Tricentis Tosca does have integration with different Tricentis tools, but the integration is geared towards a larger organization perspective. For very small organizations that have minimal licenses, the integration needs to be improvised. For example, I belong to a smaller organization that has only one license, so the capability that the tool provides for integration isn't sufficient because my company needs to have separate workspaces. When Tricentis Tosca is going to be running, it is going to use that license, but my company wants another separate workspace to record, relay, and test. This is what my team has been struggling with, and the mechanism is probably there, but that needs more time and investigation, so I can't say that I'm one hundred percent certain that Tricentis Tosca, in terms of integration for a smaller organization is insufficient.

Another area for improvement is that Tricentis Tosca is currently just a Windows-based tool which affects the market because nowadays, Windows isn't the only operating system, for example, there's also Apple or IOS that's moving much faster than Windows.

Pricing for Tricentis Tosca could be improved as well because it's very expensive.

Making Tricentis Tosca available on other operating systems is what I'd like to see in the next version of the tool. That would be beneficial. From what I've heard, you should never have the Tricentis Tosca server installed on a VM, but my company has it running on a VM and so far, there hasn't been any issue except for the VM rebooting, though I'm not sure at all if it had anything to do with having the server on the VM, or some other reasons.

I've been using Tricentis Tosca for almost two years now.

Tricentis Tosca is a very stable product, and I don't have any complaints about the tool, stability-wise.

Scaling up Tricentis Tosca would be an issue for us because of the licensing. As it's an extremely expensive product and we're a smaller organization, we don't need that many licenses, but sometimes it would be great if we could have two licenses because there are other people in the company who were trained and certified to use Tricentis Tosca. The product does provide a multi-user workspace, but we only have one license currently, so only one execution is possible at a time.

I've contacted the technical support for Tricentis Tosca. There's a support website where you can directly raise incidents with the support team and follow up. The support team is very knowledgeable about the product, though the only downside is the response time because sometimes the response isn't timely, but whenever there is any kind of response, support is very detailed and knows the product well. On a scale of one to five, with one being the worst and five being the best, technical support for Tricentis Tosca is five out of five. It's really good.

I have not tested any other SAP-related testing tools. The only tool I tested hands-on was Tricentis Tosca, and it suited the needs of my company, so it's the product we're using.

Tricentis Tosca was set up by the infrastructure team, so I don't have information on whether the initial setup was extremely straightforward or not, but I do know that there was no issue with getting the tool set up. My company has a cloud license and an on-premises license, so there are various setup options available for Tricentis Tosca.

We implemented Tricentis Tosca through our in-house team.

As for the licensing cost for Tricentis Tosca, I'm not one hundred percent sure how much it is, but I know that it's an expensive product. I wouldn't be able to rate Tricentis Tosca in terms of pricing because I don't have information on the prices of other products tested by my organization. My team tested Worksoft and that was also an expensive tool.

Few tools provide the capability to test SAP automation tools, and the majority of the products are more suitable for a larger enterprise and have higher pricing, but if you're a very technical tester, there are other tools you could utilize. Technically skilled people and technical automation testers may be able to use open source tools, but for the not-so-technical testers, only a few SAP-related tools are available, but from what I've heard, they're priced on the higher side. I won't be able to advise if Tricentis Tosca is more expensive than its competitors because I don't have pricing information for any of those tools.

My company uses Tricentis Tosca.

My advice to people looking into implementing the tool is that it's great to use, but you need to be more hands-on. Tricentis has certifications available, so the more you advance your skillset and get yourself certified, you'll learn all the mechanisms of how Tricentis Tosca can be used. So far, the tool ticked most of the boxes based on my company's needs.

I'm rating Tricentis Tosca nine out of ten. I didn't give it a perfect score because it's currently based on Windows only, and its cost is high but other than those two cons, everything has been great about the product.

My company is just a user. It has no partnership with Tricentis Tosca.

We primarily use the solution for automation testing. It integrates with other DevOps pipelines. 

The solution has improved out time to release on production. Everything's automated now, which makes everything move faster. 

The solution is model-based. I know and that's the main reason we went there. We are also using Tosca BI, which is the BI module. We're using that regularly for most of our teams. We just purchased it for our Business Intelligence. We ran a POC and then we just purchased it. 

The initial setup isn't too difficult. 

The solution does not have one catch-all product. For example, if you wanted the DB for Business Intelligence, it's a different module that you have to purchase. If you want to do API testing, you need to buy a different module. If you want to do performance testing, which we haven't bought yet, you would need to buy another module. There are a lot of modules you have to buy in order to have full-blown testing capabilities. I understand that they're breaking them up so people who don't want everything aren't forced into things they won't use. However, for those that do want all of the functionality, it can get costly. 

We've been using the solution for probably two to three years so far. 

The stability of the solution is good. It doesn't crash or freeze. there aren't bugs or glitches. 

The solution can scale quite well. We have 16 groups using it. I don't know how many individuals are on it, however, it's likely there are five people per team. We usually don't go by user when we're counting.

We do plan to increase usage in the future. We use it quite extensively already. We may be moving some legacy tools over to it. 

Technical support has been good. We are satisfied with the level of support on offer. 

We used IBM Rational or Functional Tester and it was just outdated and we needed to go down the toolset. We also wanted something that we use as a data model. 

The initial wasn't complex, it was pretty easy, however, when we did the upgrade to the latest version, which is the new way of architecting, that was more of a challenge due to the fact that we're in multiple clouds. That was more of an issue for us to upgrade due to our multiple cloud environment.

We had to work with Tosca quite a bit to get that one done. Of course, there aren't too many folks who are doing what we're doing, so that might be part of it.

The deployment took a quarter of a year. We tried to install it in our environment and that's got a lot of rules in it, and therefore it took a while. For us, the security and architecture had to be approved before we put anything into our complex environment. It also took a while to train people up on it. 

We have three staff members that handle maintenance aspects, however, they also work on different tools as well. They are not full-time on just Tosca.

We hired some consulting hours from Tosca to help us with the tech. We ran a POC, which they helped us with. Then we did have some consulting hours - maybe 30 or so. We also had them train us. It was good.

They also have self-service training. They recommend you take the self-service training before you start working with the consultants. That way you know more, and then it doesn't take as much time with the consultants. 

While our teams are seeing a great benefit, I wouldn't say we see a return on investment. ROI can be subjective.

The solution is expensive. You can do multi-year or you can do yearly in terms of a licensing agreement. You can do whatever you want.

While it's a pricey solution, it's probably more stable and has more capabilities than some of the other solutions out there.

The only other cost, aside from choosing the modules you need, is the server costs as you need to put it somewhere. 

We did look at other options before choosing Tosca, however, I cannot recall which. It was a few years ago now. We did use Gartner to help narrow down our options. 

We are end-users and customers. 

We are using the latest version of the solution, although I can't speak t the exact version number. 

We have the solution on the AWS and Azure clouds and we also have it on-premises. 

I'd rate the solution at an eight out of ten. It's stable and it works, however, the cost is high. You also need a high level of knowledge in order to use it. You can't just pull someone off the street and make them a user. There's a definite learning curve. 

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

What I find valuable is that Tricentis is always refining the test methodology. They listen to feedback from the analysts about what the testing tool should do, and then Tricentis always implements it. So all the necessary testing functions are already implemented in their tools. So whenever there is some new need for a testing capability, I can be sure that Tricentis will implement it into the Tosca Test Suite quickly, and we can use it.

Tosca's reporting features could be better. Tricentis had a reporting tool called Analytics, but it didn't function properly after they reworked it. After that, they tried a new approach with key-tracing, and that didn't work. So they don't have a good reporting solution currently, and I hope they add one soon. 

I've been using Tricentis Tosca for around 16 years.

Tosca's stability is good. However, when we upgrade, sometimes we find some defects or problems. These are usually fixed within days or two weeks if there are bigger issues. And this is once per year, usually without any bigger issues. The only other thing that sometimes causes problems is when the time path and some repositories are not on hand. Also, if the infrastructure or the network is not stable, you can have problems with the application. But, of course, that's not something the application can really prevent, like if the internet connection breaks or something like that. Especially now that almost all of us are working remotely. So you can have some defects on the network that causes some problems in the application as well.

Before, we also used Tosca for manual testing. We had, I think, 400 to 800 main users — not at the same time — but we had a lot of users then. If you know the size of your repository, then it's easy to size the server accordingly. Also, when you know your requirements, you should make sure that the infrastructure meets the requirements, then it's easier. 

The quality of Tricentis support really depends on the type of issue. When it's important, I go through the surveys, account manager quizzes, and so on. Tricentis handles the important issues quickly. And if we have smaller problems, it's usually routed to India, so we get a lot of basic questions back, and I don't like that process much. But, when it's important, we're immediately connected to the right people and get quick solutions.

Setting up Tosca is quite straightforward. The main issue is setting up your infrastructure, the network port, and all those things upfront. But when this is fine, then the installation is uncomplicated. Then, we update once a year, and it takes a few hours.

We have some integrators and consultants working for us, and we always have on-demand vendor support if something is not working. They resolve issues quickly. The vendor handles software maintenance. Our installation and maintenance can be partially done by a Tricentis consultant who works for our team. But before, it was an in-house guy. That guy left, so we hired an external consultant to do the same functions as the in-house staffer. So we have someone in the organization who is doing that. Before, it was internal and not external, but he is working basically like an internal for us.

I'm not sure if I'm at liberty to talk about the pricing, but it has some significant costs. For example, you have to pay a license and maintenance fee. Then the rest of the terms are negotiable. We have to consider what we need and what benefit we get from it. You can then make a business case and see how the licensing fits best since they have different licensing models. You have to find the right model of licensing for you and then negotiate a reasonable price. So we always make a business case, and if the business case is okay, the licensing price is also okay. It provides value for the money. It's a stable product with a lot of functionality. And as I said before, it keeps pace with all the new trends that the analysts suggest, so it's worth the money

I rate Tosca nine out of 10. So if you are considering this solution, I recommend that you make sure your team is good and stable in test definition. Also, you should build up your organization's competence in test automation. That way, you can get the most out of the tool and utilize its capabilities to benefit your organization. But there are challenges with a large organization internally. For example, we first had a central team for test automation. Then we moved to HL and de-centralized our test automation team. Unfortunately, that didn't work so well since it requires some specialized knowledge that you need to learn and to practice. So now we are trying to move again to centralized test automation and get more value for the business.

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 switched to Tosca because it's a no-code solution. That's the primary advantage because many of our functional testers lack technical knowledge and cannot write code in Java. People without coding skill can also use it. We only need to train them. Multiple functions, loops, and logical conditions are available. If you have an in-depth understanding of the Tosca framework, you can easily automate any complex application.

We're working with multiple on-premise and cloud applications, and we use Tosca's reporting tool for regulatory purposes. One of our applications is built upon BDA visual basic, and Tosca can identify the object of that application.

Tosca generally supports 90 percent of the applications. We handle dynamic applications and multiple popups that appear while running them. I've trained almost 50 people in my organization to use Tosca, and they are now doing well.

Tosca is flexible enough to work with multiple areas, like web, API, database, and retail automation. Tricentis team supports all these areas regardless of your operating system 

Recently, I've been working on an automation application. To date, I've designed almost 10,000 scripts. In addition ETL and AP automation, we are using Tosca API to automate web services.

We can also create customized functions. For example, if something isn't supported in Tricentis Tosca Commander, we can create our own function to integrate it with Tosca Commander, so we can utilize it and integrate with the macros.

We create macros in the Excel DVS, and I created multiple tools via VBA as part of the ATL automation to compare source data to the target. We just need to schedule it. We schedule that via Postcard, so the macros we created will compare the source data versus the target data. 

First, Tricentis could improve Tosca's Linux scripting. We can automate Linux scripting, but there are a few commands that Tosca doesn't support. DVS support and the object identification mechanism could also be better. 

I have worked with Tosca for six or seven years.

We don't have many issues with stability. The only problem I had was three years back. The support team came to and resolve that issue. 

Tricentis support is excellent. When we create a ticket, they'll usually resolve it in 24 hours. There is a also chat bot.

Tosca is heavy software, so the prerequisite is 4GB of RAM and a 255 GB hard disk. It takes almost 10GB of hard disk space, and the initial setup is not difficult. You only need to get the EXT, and Tosca comes with multiple programs like Commander and Executor. There are several tools, but we primarily use the Tosca Commander because it contains everything, like the execution, DHN, and reporting parts. 

There are two licenses: single user and multiple user. A multiple-user license means that several people can work together on one project and collaborate on code stored in a central location.

A single-user license is for people working alone on a one particular application. It's much cheaper than a multi-user workspace. If you are getting a large volume of licenses for an enterprise, you can probably negotiate a discount, but I'm not sure about that. 

I rate Tricentis Tosca nine out of 10. The tool has multiple features, and it covers a variety of applications, It's accessible, so anyone can use it even if they're not a technical person. But if you have some programming knowledge, you can create your own customized functions and automate any Windows application. Integration is straightforward, and test management tools are also available. 

A person can get an ES1 and ES2 certification by viewing a video tutorial before starting the actual scripting. They complete the certification work with any demo application to learn how to scan the objects, execute test cases. Tricentis supports 95 percent of applications, and it covers a broad range of areas, like DB, ETL, and website automation. 

Tricentis Tosca is a tool used for system and application testing.

The advantage of using Tricentis Tosca is that we can get started with automation without much investment on solution development, with it following a keyword-driven approach. We have the actions and verifications readily available, so you can get started on the Tricentis Tosca conversion from the first day of training, and this is the advantage we have observed from the tool.

I also like that it is a simple tool, in terms of system testing, though there are other tools now that are good competitors for Tricentis Tosca, e.g. Katalon Studio.

A disadvantage of Tricentis Tosca is that you have to customize it according to your need, during the early stages of the software. Sometimes this happens when you're not on the system testing phase, but you're very close to development, e.g. more on the upstream testing, before system testing, unit testing, etc.

For example, you have to inject something as a precondition to the solution on the test, so you have to do some presetting, you have to write some code to it, and you have to make some conditions for upstream testing. Tricentis Tosca is not recommended in that stage, but it's definitely better for system testing, with it being keyword-driven and you have the keywords readily available, especially if you compare it with other tools such as Micro Focus and TestComplete.

Though I'm not currently working with Tricentis Tosca, e.g. I don't have a project utilizing the solution, I've had experience with it in the past year.

We evaluated Micro Focus, TestComplete, and Katalon Studio.

I am in the QA side, and I have almost 20 years of experience in QA. I'm doing all the automations. My experience with commercial tools are customer specific, e.g. if the customer wants to use a specific tool. I have experience on object-based tools and other types, on the commercial side. We use OneSource libraries and the custom frameworks, so that's where I have more experience, compared to commercial tools.

I don't have any current projects with Tricentis Tosca, but my company has a partnership with Tricentis. I'm not in the delivery team, e.g. I'm on the CoE team. Our application testing is more on digitally managing application drivers, so our scope on application testing is minimal. However, everyone's going digital nowadays, e.g. there's the remote setting and other things to come, so we utilize browser-based solutions, testing, mobile, etc.

I'm part of the CoE team where our work involves solutioning, initial designs, and choosing the right tools. We don't get into the product and use the same tool for a long time, in particular, we do a POC. With Tricentis Tosca, we have asked our teams to do a POC using it, because there is nothing more important than learning the tool, so that it can be easily understandable. Based on customer demand, we have done a few POCs for the tool, so our team isn't really involved in the full lifecycle of a project.

Katalon Studio is very similar to Tricentis Tosca, and price-wise, it's lower. This is why I don't compare Tricentis Tosca with TestComplete. I compare the tool with Katalon Studio, which is an open source robot that's similar to Tricentis Tosca, but because it's a free rule, you cannot have everything from it when compared to Tricentis Tosca.

My experience or my inputs on what to add to this solution, or what I'd like to see from it in the next release, would not be great, because our team is not into applications that much. Our scope of testing the applications is minimal. We are more into the panel-based devices and smart devices, e.g. POS (point of sale) or Point of Care devices in the medical field, or input devices, aeronautical flight attendance panels, etc. Those are the areas we are involved in, so they are purely embedded domains.

I'm giving Tricentis Tosca an eight out of ten rating.