Tricentis Tosca Reviews

Mixed environment having web and desktop applications, integrating with each other and over an API Gateway. API based and Financial Services portal testing created using modern technology using C# and ReactJS.

- Brought a good environment of test automation

- Allowed a significant increase in Continuous Integration

- Great User Interface and ease of checking all your artifacts of Testing.

- Makes optimal use of Model-based Test practice in getting Object-references from the application.

- Script-less, so less maintenance headache for non-technical users also.

- Drag and drop functionality to create and re-use your Test Cases

- Excellent re-use of Excel functionality for formulas and functions.

- Conditions which let the test case branch off from the Template. Helps work out different scenarios for data.

- Has been tried out on SAP, Oracle Apps, and IBM COGNOS BI applications. With a few tweaks works well with these applications.

- IF and LOOP statements introduced with the latest version.

- Improved performance of Web-Based Tests. WHILE LOOP and IF made better and more responsive with added error recovery options.

- Intuitive based options available, along with a rudimentary record and play functionality.

- Next version will even have the visualization tools required to see the interconnections between the TCD and the Test Cases, along with the workflow in the TCD and Tests.

- New and improved visualization for multiple browsers and a totally new Wizard with TBox out of Box support has been added to the (v9.2) of TOSCA Commander.

- Access to Business Intelligence (BI) features of comparing a DB to another one, also have been added as plugins.

- Access to an Analytical Engine to view and get reports from the Test Runs.

- Version 13 has also brought in BI testing and improvements on SAP Test scenarios

- Upgrades to the newer version if extra Add-ins are installed sometimes causes weird issues.

- Needs a UI to be open and present when running the tests. Cannot visit the DOM like in Selenium.

- Needs a UI to visualize the test case development.

I have used it for the past 9 years

None seen as such, except it has a reliance on the Network for Licenses. If the network is lost, then the license will expire and crash/close the application.

Depends on the Licensing model you take up.

Customer Service:

Excellent almost 16x5 service with issue resolution within a given 24-hour time frame.

Technical Support:

- Great Customer Support, technical from the first step.

Yes, have been using HP QTP and Selenium for Test Automation. Switch was mainly due to Team constraints and management wanting to try a new tool which is easier for the Business Analysts also to collaborate with.

Setup is simple but requires learning of the tool and how it does things before you can optimally use it.

In-house implementation.

An exceptionally good ROI, as we reduced the number of Tests from 4000 to around 89 scenario's which can be run in an automated manner with additional data (so in actuality we have around 1.4M tests, which can theoretically be run without human intervention). We have a full-stack CI pipeline for running these along with JIRA (requirement gathering and test results per Story), to the final TeamCity run for each check-in to the Dev branch.

Pricing is steep if you go for the premium model. Advice would be to buy a mix of licenses, depending on the need. The Tricentis Sales are rather good at helping you with this, once you give the intent to buy. They are not just shoving you the highest premium toy/license.

Yes, evaluated TestComplete, HP UFT ALM, Selenium / SpecFlow / Cucumber.

Take the online training on Udemy before you confirm the intent to buy it.

We primarily use the solution for testing. The company's businesses are tax-free payments. We're testing the company applications around the aspects of its tax-free payment systems.

The most valuable aspect of the solution is the extremely fast setup. You can really get up and running within a very small window of time. It's great.

We like the fact that it works across mobile, desktop, web, and APIs. Due to this, the solution has a broad range of applications.

The solution needs to improve its simulation of mobile environments. Right now, that aspect is really lacking.

The solution should work to try to lessen the cost of the solution. Right now, using it is costly for companies such as ours.

We'd like to see improvement in shared repositories. The problem with the shared repository is this: as it gets bigger, as we create more test cases, and due to this, we are experiencing issues.

I've been dealing with the solution for just over a year.

The stability of the solution is excellent. It's very reliable. We don't seem to have issues with bugs and glitches. It doesn't crash or freeze. It's quite good.

The scalability of the solution is very good. We can expand it if we need to The solution doesn't give us any problems in that sense.

The technical support of the solution is very good. We've very satisfied with the level of service provided to us.

The initial setup was straightforward. It was not complex at all. It took us less than a month to have something up and running. It was very easy, and one of the solution's big selling points for our organization.

We're simply customers of Tosca. We don't have any professional relationship with the company.

The pricing of the solution is quite expensive. It's definitely not one of the cheapest options. It's very pricey.

On top of the already expensive pricing, there are add-ons that help with the basic test suite, and you have to pay more for those.

I'd rate the solution eight out of ten.

I'd recommend people do a proof of concept (POC) around Tosca and compare it to other available tools. That way, an organization will know if the solution is right for them without investing too much time into everything.

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.

The features we've found most valuable are--

• It’s a modular structure, so changes in a module are automatically updated in all relevant test cases.
• It uses a risk-based approached via a weighted requirement set.

• Not all functions are logical without certain know-how.
• Context menu in the newer versions is not ideal.

I've used it for about one year.

During an upgrade there were issues, but this was due to certain security settings on our end, and the Tosca support team was very useful in helping us with those setting and resolving the issues.

We're discussing internally with fully integrate this tool within our business.

10/10. The customer service is top-notch.

10/10. The technical support is top-notch.

In our department there was not a different solution in place.

The initial setup was relatively straightforward with support from our network department for the setting up of a common repository.

We implemented it via our in-house team in combination with Tricentis consultants.

We also looked at Worksoft.

Try it out and do a Proof of Concept.

We like the idea of reusable data classes when we are using our test cases. We work with a lot of data, and so being able to create reusable data classes is very helpful to us.

The primary driver for us is that it puts automation into the hands of non-technical testers. Previous programs, if you’re not a programmer, you can forget about it, but with TOSCA it’s easier to get information and start automating your own tests.

So far, all our issues have had to do with our unfamiliarity with the product.

We are in a preparation phase – we haven’t seen everything yet. We purchased it about six or seven months ago, and started actively creating tests in the last six weeks.

No issues encountered.

No issues encountered.

No issues encountered.

It's excellent, 9/10.

It’s excellent, 9/10, as the response times have been quick and there haven’t been any problems.

Initial setup was straightforward. It took a little bit of juggling to get a central database set up as defaults to working in isolation, but other than that it was OK.

We did it in-house.

TOSCA was recommended, so we didn’t look into anything else. Our software provider said it could support their solution so we went for it. We had looked into HP UFT and Smartbear. We had used HP UFT but are fading away from them.

Be prepared to change how you approach test automation – definitely a mindset shift. It's highly configurable so you want to make good use of that. Don’t be afraid to ask for help from Tricentis, they will get back to you. Have a good bank balance because it’s not cheap.

Primarily test automation for webshops based on PHP code. It was satisfying as long as the GUI did not change permanently.

It did not improve because the GUI was not static, so it was not possible to write tests for a GUI that was in progress.

The XScan was great because it was a handy way to automate on a surface which made it very easy and simple.

It should be more flexible when using the modules; it is kind of frozen there. They should be made more dynamic.

There are a lot of features that I love within Tosca. To name a few:

• Model-based automation
• Scripting knowledge is not required
• Requirement traceability
• Usage of built-in aid packs

Before implementing Tosca, the average time that we took for completing regression was about four days. After we started using Tosca, it has been reduced to six hours.

I personally feel like the pricing is a little bit on the high end.

I have been using Tosca for almost four years.

As of now, I have not encountered any deployment issues.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Tosca customer service is one of the best in its class.

The people involved in technical support really know what they are doing. This significantly reduces the amount of time it takes the end user to find solutions.

I was using a different solution, but it required scripting knowledge, which most of my team members did not have.

An in-house team implemented it.

Pricing is a bit on the higher end.

Before choosing, we evaluated QTP, Selenium, and so on.