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.

We use this product for testing and trying to make solutions work.

This product contains a lot of functionality.

It can provide all levels of testing from design to execution to reporting. I like it because everything is available in one place.

When people start using this product, there is a learning curve. For people who were using another product, whether an open-source one like TestComplete or a commercial product, they are unable to use this solution immediately because it is much different. You need to spend much more time learning the tool and how to use it, compared to others.

When they developed the tool, they created their own rules and you need training for the people who will be using it.

We have been using Tricentis Tosca for about six months.

I would say it's a stable solution.

I have not used to to the point where I needed to scale it.

Our entire team is using it, which is more than five people.

I have been in contact with technical support and they have been very responsive. I can't complain.

I have also been using TestComplete. It is a simpler product to use and I was learning through using it. I didn't have to do any training. There were points where I needed to check the documentation concerning limitations

The initial setup was very straightforward. I did not find it to be complex and I don't remember having any problems. There was nothing spectacular about it.

Overall, the product works fine. With respect to errors in the product, there is nothing in particular that comes to mind. If there were issues then I was always able to work my way around them.

I would rate this solution an eight out of ten.

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.

• Dynamic test case creation: Tosca lets you create automated test cases in no time. You can also convert your manual test cases into automated in a matter of seconds.
• Optimize, manage and automate: It lets you jot down your requirements, design test cases, automate and analyse your test results within one GUI.
• Scriptless automation:Testers can test without worrying about writing code.
• Supports both GUI as well as non-UI testing.
• Test case design: Really lets you think about your test approach and strategy, It lets you automatically generate all the possible (and required) permutations and combinations of the functionality to be tested.

We had this huge customer application (Java based) which needed to be tested end to end. Tosca let us execute around 400 test cases overnight. Hence, it saved a lot of time and brought value for our - and the vendor's :) - esteemed client.

Tricentis has vast and helpful documentation, including the Tosca manuals, along with a detailed description of each section that also contains various tips and techniques. Along with this documentation Tricentis has provided some videos, which are really helpful and help us understand the concept very quickly (and if we want to go into detail, then we can always refer to the detailed manual later).

It would be great if there are more video tutorials on the vendor's support website, at least for commonly used functionalities.

It's been over five years now; have been using it since version 7.6.

I have not encountered any deployment issues in my project.

I have not yet encountered any stability issues.

Customer service is excellent.

Technical support is excellent.

The vendors' videos and webinars are of great help, so I would like them to keep coming up with more.

Tosca Continuous Integration (Tosca CI) - today's fast pace agile environment needs fast feedback. Working along with the development team and being able to test as soon as the code is available; gives the organisation an edge!

Tosca Continuous Integration allows you to exactly achieve that.

We have implemented Tosca CI, it allows us to test as soon as the code is deployed into the lower environment. Automated sanity, smoke tests have been configured to run every time there is a code deployment. The sanity/smoke tests are triggered automatically from a build server. After the test finishes, a Junit result file is generated and fed back to the build server.

This saves us significant amount of time by avoiding additional co-ordination/follow-ups required for sanity/smoke test. 

The Junit result file gets overwritten each time the build is triggered from Jenkins or Bamboo. It would be nice to have the result XML files stored.

Only minor issues.

The connection between the CI client and remote machine dropped off when certain standard Tosca modules were used in the test cases.

Example: TC Send Key, TC Name To Buffer

No issues so far.

Customer service is reasonably good.

There were a few hiccups on the way with the configuration files. 

Business dynamic steering and table steering.

For example, you can make templates and share them with storage elements. We use it in our main, regressive, HTML, and web-case tests.

At the moment, none. In the latest version I don’t see much room for improvement.

I've used it for six years.

In the past there were.

The product is stable; no problems with stability features.

We had in the past, but those are gone in the latest versions. In the beginning there were problems with scaling up, but those are gone as well.

We had QA Windrunner, which was running out of its maintenance lifecycle. Also, the product wasn’t very good as it caused problems, was only a tool for testing automation, and we needed a tool that could be used for several purposes like reporting, putting in requests, and data storage. Testsuite accomplishes what a lot of different tools did before. Now, three or so tools are no longer needed, and our testing is all unified in TOSCA.

It's very good.

It's very good.

It was implemented through a vendor team – our team members had done a TOSCA certification so they worked together.

The best way to look into the solution, you have to experience things for yourself. Have technical support from the beginning so that you have guidance early on.

We use it to automate testing. In terms of the version, we're up to date. We're on the latest version. 

It speeds up automation processes within testing.

The use of automation is most valuable.

There should be ease of data manipulation within automation test cases.

There should be better testing in the ETL, warehouse, or big data environment. They need to look at the speed of that and how they do that type of testing.

There should be better support. We should be able to speak to somebody.

I have been using this solution for six months.

The product is stable, but it can be a little slow, but that's a consequence of the fact that you're able to automate very quickly.

If you buy more licenses, it's scalable. 

We just have a single instance, and we have multiple users with different projects.

Their technical support is fairly good, but it's all done through email, which is a little difficult.

I've used a lot of different automation tools. I'm a contractor. I go into different organizations. So, I didn't really switch. This company was using it.

It is fairly easy. The worst thing about it is grabbing a license every time you log in. That takes a little bit of time.

The deployment duration depends on whether you use the on-premise version or cloud version. It takes a few hours for the on-premise version.

In terms of the implementation strategy, we just implemented the tool, did the training, and then started moving testing over to the tool.

We did it ourselves. We had just one person for the deployment.

We have seen an ROI because we are able to automate test scripts much quicker.

It is expensive. There is also the training cost, but it does speed up the process. So, you get a return on investment.

I evaluated the freeware tools.

When reviewing the tool, you should make sure that any automation you've already got integrates fully with the Tosca tool. That's the biggest thing. Migration of any current automation is potentially a really difficult process.

I'd give it an eight out of ten.

We use Tosca to automate progressive and regressive tests. About 60 people in my company are currently using it.

What I find valuable is that Tricentis is always refining the test methodology. They listen to feedback from the analysts about what the testing tool should do, and then Tricentis always implements it. So all the necessary testing functions are already implemented in their tools. So whenever there is some new need for a testing capability, I can be sure that Tricentis will implement it into the Tosca Test Suite quickly, and we can use it.

Tosca's reporting features could be better. Tricentis had a reporting tool called Analytics, but it didn't function properly after they reworked it. After that, they tried a new approach with key-tracing, and that didn't work. So they don't have a good reporting solution currently, and I hope they add one soon. 

I've been using Tricentis Tosca for around 16 years.

Tosca's stability is good. However, when we upgrade, sometimes we find some defects or problems. These are usually fixed within days or two weeks if there are bigger issues. And this is once per year, usually without any bigger issues. The only other thing that sometimes causes problems is when the time path and some repositories are not on hand. Also, if the infrastructure or the network is not stable, you can have problems with the application. But, of course, that's not something the application can really prevent, like if the internet connection breaks or something like that. Especially now that almost all of us are working remotely. So you can have some defects on the network that causes some problems in the application as well.

Before, we also used Tosca for manual testing. We had, I think, 400 to 800 main users — not at the same time — but we had a lot of users then. If you know the size of your repository, then it's easy to size the server accordingly. Also, when you know your requirements, you should make sure that the infrastructure meets the requirements, then it's easier. 

The quality of Tricentis support really depends on the type of issue. When it's important, I go through the surveys, account manager quizzes, and so on. Tricentis handles the important issues quickly. And if we have smaller problems, it's usually routed to India, so we get a lot of basic questions back, and I don't like that process much. But, when it's important, we're immediately connected to the right people and get quick solutions.

Setting up Tosca is quite straightforward. The main issue is setting up your infrastructure, the network port, and all those things upfront. But when this is fine, then the installation is uncomplicated. Then, we update once a year, and it takes a few hours.

We have some integrators and consultants working for us, and we always have on-demand vendor support if something is not working. They resolve issues quickly. The vendor handles software maintenance. Our installation and maintenance can be partially done by a Tricentis consultant who works for our team. But before, it was an in-house guy. That guy left, so we hired an external consultant to do the same functions as the in-house staffer. So we have someone in the organization who is doing that. Before, it was internal and not external, but he is working basically like an internal for us.

I'm not sure if I'm at liberty to talk about the pricing, but it has some significant costs. For example, you have to pay a license and maintenance fee. Then the rest of the terms are negotiable. We have to consider what we need and what benefit we get from it. You can then make a business case and see how the licensing fits best since they have different licensing models. You have to find the right model of licensing for you and then negotiate a reasonable price. So we always make a business case, and if the business case is okay, the licensing price is also okay. It provides value for the money. It's a stable product with a lot of functionality. And as I said before, it keeps pace with all the new trends that the analysts suggest, so it's worth the money

I rate Tosca nine out of 10. So if you are considering this solution, I recommend that you make sure your team is good and stable in test definition. Also, you should build up your organization's competence in test automation. That way, you can get the most out of the tool and utilize its capabilities to benefit your organization. But there are challenges with a large organization internally. For example, we first had a central team for test automation. Then we moved to HL and de-centralized our test automation team. Unfortunately, that didn't work so well since it requires some specialized knowledge that you need to learn and to practice. So now we are trying to move again to centralized test automation and get more value for the business.