Tricentis Tosca Reviews

I mostly use the TOSCA Commander to create test cases. I also utilize the Tbox feature to automate complex test scenarios. Lastly, I find the requirements linking very useful in analysis after a release (i.e. test coverage, etc.).

The product is very useful in keeping track of test execution and coverage. This is because it has a feature called Execution List which shows resources and the test cases they have executed. There is also a tab for Requirements where the test cases can be linked.

So, by combining those two together, you will be able to see which test cases are mapped to requirements, and if they have been executed. You will also see the number of passed and failed test cases. It is very easy to use once you know all the features. It barely crashes and recovers gracefully most of the time.

The product, at times, does not recognize objects, especially in web applications. It would be good to have that fixed in the next version. As a work around, you have to use the feature called TBox which allows you to scan complex objects.

I have been using it for more than six months.

No issues encountered.

No issues encountered.

No issues encountered.

The initial setup was hassle free. Although, it would be great if the documentation for the initial set up would include more screenshots and a troubleshooting section.

For our applications, it makes the test cases. So far, we have been quite happy with it. So, we don't have any complaints.

We build the test cases, then we just need run it by one person to get feedback right away. Otherwise, it would require planning with certain testers.

Compared to other tools we have been looking at, you don't have to be a programmer to operate it, though it helps. It also a product that can be used by business people.

• It needs better integration with JIRA.
• I would like a better user interface.

It is stable.

It is scalable.

We are satisfied with the support of Tricentis so far.

Setup wasn't that straightforward; it was more complex. It all depends on the environment, because there were a lot of errors on our applications. Therefore, it wasn't an easy setup for us. 

It took time to begin setting up for the first time because it's not a regular setup. It took us a week to set up.

We hired a consultant to figure out all the tools in our company and how they fit in our company before we purchased the solution.

We also evaluated HPE, IBM Rational Functional Tester, and Ranorex. However, for us, Tosca was the perfect choice.

Figure out your requirements and environment.

We had the impression Tosca would be the perfect fit for us. We did a proof of concept test with all our applications, Tosca was able to work with them and drive the proof of concept goal. Finally, we made a decision a year ago to work with Tricentis Tosca. We are quite happy with the product. 

Tosca is a model based component tool and also quite flexible in terms of the customization required for most of the applications, if objects are not recognized. It allows manual testers to pick up automation, because it is a scriptless tool. Reporting is well managed within Tosca and there is no requirement to build a framework around it.

We are only using Tosca for our test automation. It helps the business testers to get involved and be a part of automation. It helps us define the right coverage by defining the scope in the test case design section. This tool has test data management capability along with test management.

• Objects re-scanning (recognizing the objects again)
• Providing features to highlight the objects
• The user guide/help document needs to be improved for better understanding of the tool and its features.
• ScratchBook execution needs to be improved as Tosca crashes multiple times.

I have been using Tosca for the past two years.

If the Tosca repository becomes huge in size, then you might face performance issues. Tosca crashes many times and the best practice is to keep saving your work frequently to avoid re-work.

There were no scalability issues.

Technical support is available via chat or by raising an incident. They are often able to resolve minor issues. It takes really long to resolve major issues and we have to wait for them.

I have been working on different test automation tools and I was introduced to Tosca because of the technology that it supported for our applications. The current test automation tool was unable to provide a solution for our .NET Windows-based application, which Tosca provided out-of-the-box.

The initial setup was not very complex. The Tricentis team provided support in terms of setting up the project and assisting during the initial days to get us used to the tool.

It is an expensive tool compared to other test automation tools. It has a lot of advantages over other tools. They provide different types of licensing like cloud, Node locked, and floating licenses.

We did Proof of Concept with other automation tools, such as UFT and TestPartner, but we found Tosca to be a better tool.

I would definitely recommend this tool. It is user friendly, once you get used to it, and it is easy to implement. You might have to struggle initially to understand Tosca and its approach.

Our whole team that is working on Tricentis Tosca has done training to receive certifications in automation engineering and test design.

Tricentis Tosca can be used for software testing with automation.

The solution has plenty of features compared to other solutions.

Tricentis Tosca's performance could be better. Sometimes when we are remapping or when it is loading it can take a lot of time. There are free solutions that have better performance in this area.

I have been using Tricentis Tosca within the last 12 months.

The technical support of Tricentis Tosca is good. They have been helpful and resolved our problem.

The installation was straightforward.

I have evaluated other solutions.

I would recommend this solution to others. It has the capability of doing many types of tests.

I rate Tricentis Tosca a seven out of ten.

While we started implementation with a focus on testing automation, the Risk Management feature is one we are seeing as very valuable in our environment, allowing us to better focus on critical testing.

It has allowed us to have a highly reusable Regression Test suite. We have already been able to run it for an SAP upgrade and plan on using it on a regular basis (weekly) going forward.

The record and play is still a new feature and while SAP has been added to the latest version, it is still lacking usefulness for common repository setups.

We've been using it for about 8 months

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

We have had great customer service so far. Support has been responsive and helpful.

Technical support has been pretty responsive so far. They have provided solutions to most of our challenges and provide work arounds when no solutions were available.

The tool is very different than other testing tools and it is important to explain some of these different to all the stakeholders to ensure they really understand the benefits at their level.

By that I mean that a tester might see benefit in the ease of automation but a business user will see benefit in the risk coverage visualization, for example.

• Test case design: Integrated test data management in the tool itself
• Web services automation: Easier API testing
• DevOps: Testing starts as soon as development gets completed
• Service Virtualization: Early automation

It is quick and easy to maintain automation with Agile implementation.

I would like to see defect raising and tracking.

I've used it for almost a year.

There were sometimes issues with stability.

There were sometimes issues with scalability.

Technical support is very good.

We switched as there is no scripting required. The framework is inbuilt, hence maintenance is easier.

The setup was straightforward.

Licenses are expensive, but they are worth using.

Go for the product if you are looking for faster automation.