Tricentis Tosca Reviews

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 fast-pace, ever-evolving test automation tool that can solve today's testing requirements and provide fast feedback. The recent version of Tosca introduces a number of exciting features, such as:

• Web analytics
• Better identification of test objects
• Record manual and automated test cases

• Easier to maintain than any other tool in the class
• Fast turnaround
• Ease of integration with third-party tools

Run time test execution status: They have improved on this a bit by introducing a progress bar. However, it can be further improved.

I have used it for 3.5 years.

I encountered deployment issues. However, their support is reasonably good and after some investigation, they finally resolved the problem.

I only encountered stability issues with versions lower than 8.x.

The current version is fairly stable.

I have not encountered any scalability issues.; it is very easy to scale.

Customer service is reasonably good. The live chat facility works just fine.

I have experienced that the tech support team is a mix of experienced and relatively newer staff. Most of the time, the queries get resolved.

The staff is nice and ready to help.

I previously used a different solution. I switched to Tosca because it has much faster turnaround time and is very easy to scale up.

Overall setup is reasonably simple. Only a few other settings need to be done before you can start using it, but it depends on what you need.

An in-house team implemented it.

Pricing and licensing is on the relatively higher side, when compared with other tools in the class. However, you start realising the benefits quite quickly.

Before choosing, I evaluated QTP and Selenium, along with Tosca Testsuite.

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

We have to automate thousands of test cases and complete end-to-end SAP on business processes. To manually execute these tasks, it would take us at least two months. By automating these tasks using Tosca, now it takes five to 10 days maximum. Tricentis Tosca is a codeless or scriptless automation tool.

Test case design and test data management are the most valuable features for us.

With regard to areas of improvement, report customization should be easier. It would be good if Tosca could provide standard reports for at least 20 variants. At present, there are only three to four variants.

The mobile engine needs to be faster and easier to use; it is a bit cumbersome. Also, the object identification in the mobile engine needs improvement.

I would like to see easy-to-use customizations for reports in the next release.

I've been using Tricentis Tosca for the last nine years.

In terms of stability, I would rate the solution at nine out of ten.

I would rate Tosca's scalability at eight out of ten. We have 10 users and 10 exemption licenses in our organization. We plan to increase usage in the near future.

Initially, we were able to create a case. Right now, that function is not very useful. We also have to request remote access. In addition, sending large files is a bit cumbersome because our organization's policy does not allow us to upload anything to Tricentis' cloud or network.

Thus, I would rate technical support at six on a scale from one to ten.

Neutral

We used Micro Focus UFT and SmartBear. UFT requires a framework each time, and SmartBear requires coding. Both of these solutions had limitations with regard to our enterprise-level technology stack, and therefore, we decided to go with Tricentis Tosca.

The initial setup is easy, and I would rate it at eight out of ten. The deployment process took at least 48 to 72 hours.

We deployed it ourselves with help from third-party teams. We had four people involved in the deployment including engineers and a manager.

If you are purchasing less than five licenses, then the pricing is high. On a scale from one to ten, with one being low and ten being high pricing, I would rate this solution at eight.

Tricentis Tosca does not provide much support for reports and mobile automation. The speed of execution of mobile automation is low. Also, test case creation and the creation of models take a lot of time in the mobile engine.

Overall, I would rate Tricentis Tosca at eight on a scale from one to ten with one being the worst and ten being the best.

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 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.

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.

I use the solution for software validation.

The product's database capacity should be increased. The product has certain shortcomings in cloud storage. From an improvement perspective, cloud storage must offer more features.

I have been using Tricentis Tosca for a year. I am a user of the solution.

The product is not very stable when used with cloud storage. It is very hard to load the screen, making it difficult to use the tool in cloud storage.

Scalability-wise, I rate the solution an eight out of ten.

My whole organization uses the product.

The product is used every day.

There was another product I had experience with in my previous organization.

I rate the product's initial setup phase a seven on a scale of one to ten, where one is easy and ten is difficult.

The solution is deployed on the cloud model.

The solution can be deployed in a few hours.

Speaking about the feature of the product that has the largest impact on our company's testing process, I would say that I use Selenium to take care of the coding part. In Tricentis Tosca, we can't use Git code, considering the user-based experience and UI for the testing process.

Speaking about the codeless test creation feature in Tricentis Tosca, I would say that in some of the software where the quality assurance team does the verification, Selenium is used by quality analysts. In Selenium, we used to write the codes to check basic stuff. In Tricentis Tosca, we don't have to write any scripts.

Integrating the product into my company's CI/CD pipeline affected the release cycles in a good way.

For beginners, the product is good, especially for those who are interested in the quality side of software testing.

Considering the emerging trends in the automation space, I would say that Tricentis Tosca is a good software.

I rate the tool a seven and a half out of ten.

The tool's most valuable feature is Tosca Commander. 

The tool lags in client-based applications. We have also encountered issues with the features in integrations. 

I have been working with the product for five years. 

The tool is 99 percent stable if you follow its key specifications and best practices. 

From the automation perspective, Tricentis Tosca's scalability is good. 

We have a portal to contact the support team. 

Positive

The tool's deployment and maintenance are easy. We get access to the knowledge-based documents in the portal. Deployment can be completed in five to ten minutes. 

The tool is worth its cost. 

Tricentis Tosca should improve its pricing. It is expensive. 

I rate Tricentis Tosca an eight out of ten.