Tricentis Tosca Reviews

Image recognition: It has allowed us to automate a GUI section of our product which involves drawing different topologies.

I’m aware that other tools have this feature, but the whole test suite, it makes it good enough for us not to look for something else.

No, not in global organization; we are the only ones who are using it in our location (Austria), but in our team, it changed the testing workflow:

Every second week we release a candidate, and from two weeks of hard manual testing, we are testing now only a few days (four to five), the new fixed tickets and running in parallel - the regression. We have more time to increase the regression portfolio and also decrease long delays with documentation.

Running the regression – if multiple lists are executed at once or if a list contains 200+ tests, it’s a pain to stop the execution.

I have been using it for almost four years.

A few times, it just crashed. I didn’t encounter this issue with Tosca 8 and Tosca 9, but the PC was running for days so I cannot blame only Tosca. I assume Windows played its role, too.

No, not so far. We have around 3500+ TCS.

Nice and friendly, however not always coming up with the solution we were expecting. For example, after changing from Tosca 9 to Tosca 10, we were not able to run some test cases for an older tool (it was developed with Java 1.5). The solution from their side was to request a change request even if it worked in the past. In the end, we just downgraded and we are running those test cases with Tosca 9.

No.

Of the tool, yes. Managing to trigger our application was not so straightforward (because of our company access policy). We had to write some batch scripts for it, then it worked fine.

Expensive, but for long-term projects, it is paying back.

Yes, there was an analysis, but I was not part of the company at that time.

It is a good tool, but could be better in some aspects.

It’s relatively easy to set it up and intuitive to create test cases for non-developers. If you come from the development side you will feel some limitations, but I was always able to find a workaround.

The tool can be handled without any knowledge in parameterisation, especially the TestCaseDesign which makes the tool mighty and stable - even when releases in the tested software are subjected to deep code changes. The maintenance of the test tool is manageble.

I managed a test set over all areas for a retail bank alone for about three years with almost 1,000 test cases. I automated the starts overnight, and paralleled them on virtual clients. Then, I needed 24 hours for generating synthetic test data, regression test runs, and analyses. The runs were stable, and I could report many defects before the start of the manual tests.

The Testmanagement option are still weak - improvement is outlined, but not yet visible. I expect first impressions of this solution at accelerate in Vienna, october 2017.

Actually I upgrade the testsuite as often as possible - in my function as consultant I want to feel and test the improvements as soon as they are released. 10.3 was not stable enough for my expectations.

Not yet.

With testuite 10.3 - so I derelease back to 10.2.

Not yet - as the environments were always well set up.

This is a point were Tricentis has to improve - customer support seems to be overflood in the last few months.

Basically it's very high, the support is fast, friendly and qualified - if reachable. Which was not always the case in the last three months.

The initial setup should be done highly structured, and by qualified specialists. This is the only efficient way of a stable test set.

I would definitely recommend a vendor team for the implementation!

We felt the benefits within the first year. I would recommend in-house management.

There was no need for us to do so.

It is a mighty and stable tool, but it needs qualified and motivated staff to work with and manage it.

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

The scanner helps us to define many tests with one scan.

Tests written once can be reused across different projects

I would like to see the availability of more libraries

We have you used this solution for two years.

I did not encounter any issues with stability.

I did not encounter any issues with scalability.

I would rate the level of technical support as average.

We used Soap UI and Selenium (Open source tools). We switched to Tosca because the organization decided to make the switch.

I taught myself how to do the set up, so it was OK.

There are many products on the market. Providing more libraries for the price will be an option that could help.

We evaluated other options before choosing this solution.

It is a good product, with online tutorials, knowledge base, etc.

Valuable features include generating data including ECP, BVC and risk-based opportunities:

• If the data is vast, we may miss a few scenarios. To avoid this, the Tosca tool provides an inbuilt feature.
• Classifying tests into two types: Equivalence partitioning (+.-) and boundary value tests (inbuilt feature of Tosca).
• Risk-based opportunities are identified based on customer weightage for the modules (inbuilt feature of Tosca).

It has decreased the time for generating test data and risk-based opportunities which has helped us to cover key areas.

The Support TDD and BDD could be improved.

We have been using the product for a year, but we have been using HPE products for seven years.

We encountered a stability issue with Tosca, but it was rectified.

We did not encounter any issues with scalability.

I would give technical support a rating of an eight out of 10.

We switched from Python for fast access of files.

The setup was straightforward.

The pricing of Tosca and HPE is high.

We evaluated SmartBear.

I prefer TDD with SpecFlow and Cucumber using a coded UI. These tools need to be integrated with Tosca to drive the TDD approach in automation.

I liked the "no required scripting" part as most of the people in my team are not skilled QAs and half of the team reside offshore, thus it suited to most of our requirements.

We ended up going back to Selenium as this tool was very slow with the web applications. Also, for any new functionality, it requires customization that in turn required training with no guarantee that it may work with future releases.

They have to create some discussion forum, we cannot always rely on some expert to respond to the queries. Also, everything requires additional costs. They need to have better documentation, forums, and support.

I have used it in one of my smaller projects so as to evaluate if we can use it as an alternative to our Selenium Keyword Driven Framework. I have used it only for two weeks with the 14-day free trial.

The level of technical support is average. I reported that the web application response was very slow and I never really got a real solution. Instead, I sent out too many emails just to explain to them what the problem was.

We have used Selenium WebDriver and still are using the same solution.

The model-based scriptless automation is the most valuable feature because it needs less maintenance as compared to script-based automation.

Tricentis Tosca supports 35 technologies, such as web, mobile, Salesforce, Java, SAP, ServiceMax, and Flash applications.

Tosca follows the shift-left approach. A new resource can start automation on the first day of its project.

Parallel execution is not yet implemented for Tosca. This means you can't execute the same test case on multiple machines remotely. For execution, test cases have to be present on that machine. Even while, a test case is executed you can't perform any other activity; you end up sitting idle during execution.

I have used this solution for 18 months.

There were no stability issues.

There were no scalability issues.

Technical support is fair.

Previously, we were using Selenium. We switched to Tosca due to the less maintenance aspect and the wide technology support which it provides.

Configuration is easy.

No idea about the licensing cost.

Whilst selecting a vendor, we look for factors such as technical support and maintenance.

If you are looking for automation of the packaged application and less maintenance, then go for Tosca.