Tricentis Tosca Reviews

Below are the features that are the most valuable in regards to this product:

• With one click, it will scan all the elements on the screen, so that the user can select the required elements for automation tests.
• Exploratory testing gives an option to record a video, has interactive steps to capture a manual test case flow, and it can be converted to a PDF document with links for the video.
• Using exploratory testing, we can send an email to record manual test cases to the business analysts (BAs) who never need a product to be installed in their machine. The recorded files can be stored on a common server (that needs to be set up separately) or they can send those files to the intended automation team via emails.
• Not much in the way of programming skills is required to use this product.

Our organization is satisfied with this product on the technical side of it, but our organization was looking for the reporting part of this product since they undergo an auditing process for each year. The reports should be improved for the Tricentis Tosca product.

They need to improve on the reports after the execution of automation tests, since all the current organizations are looking for detailed graphical reports.

My previous company uses an application which will create a purchase order for their products, so my company wants to track all the purchase orders and the accounts that have been used for testing. We have set up data and automated tests in Tricentis Tosca. Using the Execution Folder (in Tosca) we are able to execute automated tests which gives detailed information for each run/execution. However, we were expecting a report for each execution like what scenario executed, what data was used (dummy customer accounts) and the resulting purchase order numbers.

Tricentis Tosca is able to export the execution results in Excel/PDF format but our company was expecting customized reports, so I mentioned this as room for improvement.

I have worked on this product for six months.

There are no issues with the stability part of the product.

There are no issues with the scalability of the product.

I would rate the technical support a 9/10, their turnover time is very good.

We have used HPE UFT (formerly known as QTP) and Selenium, but some of the critical applications that we needed required different automation tools so we switched to Tricentis Tosca.

The product's setup is pretty much straightforward, no issues in regards to that.

I am not much involved in the pricing and licensing.

We explored tools such as HPE QTP/UFT, Selenium, Ranorex and TestComplete but these tools require some specific programming skills to start. Tricentis Tosca doesn’t require any programming skills and it’s a codeless automation.

For a manual tester who wants to become an automation specialist with no programming skills, this is the right tool for the future.

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

The ability to pick up when a desktop picks up, which makes it much faster to run tests. Also, its ability to work across multiple systems is very useful.

More and more artificial intelligence (AI) is coming in. So, some amount of AI to create natural language processing (NLP)-based test cases and manage defects would be very helpful. This is because the technologies have evolved in the last five to six months, so there is a potential opportunity there.

For creating test scenarios, looking at defects, historical defects, and kind of putting in generative AI would add value. 

I have been using this solution for around four years. 

I would rate the stability a nine out of ten. 

I would rate the scalability a nine out of ten. We have enterprise-level customers because this is not ideal for smaller customers. Smaller customers tend to be using open source tools, but actually, to get it to the enterprise level, Tricentis is used a lot.

I would rate my experience with the initial setup an eight out of ten, where one is easy, and ten is difficult to set up. It is usually deployed on public and hybrid.

I would rate the pricing a seven out of ten, where one is cheap, and ten is expensive. It is on the higher side. There are open-source tools available, and there are other tools available that are much smaller. If you are looking at commercials, then there are options available that are newer.

So, if you need to accelerate the delivery of your solution and leverage the low-code, no-code platform, that's where you can actually bring in quite a lot of automation with the region type in Tricentis Tosca. Maintaining your test scenarios, running them immediately to create mind maps, and then using new-generation tools like xMine to integrate with Tricentis Tosca can significantly reduce the testing cycle time from a typical 20-35% of the software engineering cycle to as low as 10%. This can significantly improve the turnaround time for decision-making.

I would rate it a seven out of ten. There are lots of alternatives that are available at a good price point. So when you are working with large customers who have big budgets, bigger budgets, certain places are something that they are going to take up. When they are working with medium-sized customers, potentially, the signatures could actually address that.

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 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 primarily use it as an MBT, a model-based automation tool.

The solution is script-less, so you don't need IT knowledge to use the solution in an operational way. This is the most valuable feature. It's also only one of two or three tools that can do good automation on SAP, and in my opinion, it's the best of those.

The test sheet is very good.

There are algorithms that allow you to generate various test cases that guarantee maximum coverage.

If Tosca wants to rule on the RPA world, they have to give some security guarantee.

The solution should work with the Linux platform. Right now, it only runs on Windows.

The solution could use different modules that would be useful to an organization. Examples of modules they could add include robotic process automation, analytics, and business intelligence among others.

The stability of the solution is good.

Technical support is very efficient. There's a helpline, but there's also an academy and training support.

The initial setup is very easy. Deployment took about half a day. If you want to deploy it on just the local machine, it will only take about ten minutes. However, if you want to deploy it to an environment with a common repository in a collaborative multi-user mode on a database that allows some concurrent shared work, it might take up to one day.

We use the on-premises deployment model.

My advice to others is to get training by a professional. This will help anyone use the product. Tosca allows users, even if they don't have some IT knowledge, to quickly start and use Tosca after about two weeks. You can take any business person, and just offer them good training. After about two weeks or a month, they could be independent and will be able to automate some complex scenarios. You don't have to be an IT specialist to handle the product. 

I'd rate the solution eight 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. 

Tosca has been used for automated testing with our business process management tool, known as Athium, as well as our GRC tool, Archer.

It assists us in putting together automated testing for those two platforms in order to manage test coverage and do it in an automated manner as opposed to how it was done manually.

The most valuable aspect of using Tosca is that its user interfaces are intuitive. 

With the resources, we can quickly learn the product. You can quickly build automated testing, manage it, and have it run on a regular basis to ensure that there are no issues. It gave us a greater level of confidence when we were carrying out those tasks.

Some of those testing with other code-based setting frameworks found it to be much more fragile. As a result, managing and updating were much more difficult than with Tosca.

In terms of tool limitations, there is not a lot that the vendor would need to develop at this time. I believe that the Tosca tool's setup capabilities, as well as functionaries, could easily assist us in a very nice way with our automated testing effort.

There are some things that we would need to do on an organizational level. We did not implement the process of our primary automated testing tool. The IT teams are still relying on the coding framework, which is either Ruby cucumber or Java cucumber, to complete a large portion of the automated testing.

We would have to delegate a large portion of that work to Tosca, which would rely heavily on training the existing automated testing team. Also, we would have to obtain a license for the product and ensure that all of them are operational.

While the initial setup was straightforward, we required assistance with the configuration to ensure that everything was done correctly.

I have been working with Tricentis Tosca for a year and a half.

The product is extremely stable and provides excellent value. 

We no longer have to manage the stability, and we no longer have to perform tests manually.

It gives us a much better idea of what kind of test coverage we have, as well as whether or not the system will be stable with automated testing in place.

The stability has been great.

I would give them a nine out of ten for their assistance. They were responsive, as well as assisting us to be fully enabled as soon as possible.

Our teams use qTest for a lot of test management and test planning, and some of the IT teams use qTest heavily, whereas a couple of the application teams, use Tosca.

The initial setup was simple, but there were a few areas where we needed to consult with the support team.

The support team was extremely helpful in assisting us in configuring the system correctly as well as providing and sharing some best practices for setup and configurations.

They are probably more expensive than other comparable tools, but you also get the full suite of testing tools. 

It has a wide range of capabilities. And, even though you pay probably twice as much, you get a lot more for your money.

If the teams are implementing and they are doing agile development and want to stay on track with their agile deliveries, the automated testing goes hand in hand. Tosca can be an excellent enabler for you to be able to do the testing at a much faster pace than if you were trying to do that with other manual testing and that does not slow you down.

It works very well if the organization is trying to move toward a more agile approach, and the ability to do automated testing lends itself very well to it.

I would rate Tricentis Tosca a nine out of ten. It's pretty good.