Tricentis Tosca Reviews

We are primarily using this product as an automation tool, for regression, and as a revision tool. 

Using the automation tool, I can transfer test cases that are being done manually to ones that are automated. After about 30 such instances, I use the regression system from the suite to create all possible combinations of test cases to try with the new version. This gives us an overview of how the software is performing. Also, when major updates take place, we re-run all of the regression tests to make sure that it still conforms to the requirements.

The automation testing functionality is very powerful.

This tool is very easy to use and I think that anyone can come in, having no experience with it, and within four to six months be comfortable with it.

The graphical interface means that you don't have to write any code.

The interface is very organized. You can find folders and settings for everything that you need, and you can easily connect things together.  

I would like to see better integration with other testing tools. There is full integration with Selenium and having this with other tools would be good.

Integration with other programming languages would also be helpful.

I have been using Tricentis Tosca for the past three years.

I have not really found many problems or bugs when using this product, so stability has not been an issue.

Tricentis Tosca is very scalable. You can easily move from a small test suite to a larger test suit, which I think is pretty good. We about 100 users in the organization.

I have not been in touch with technical support from the vendor.

I also have experience with Selenium HQ, Katalon Studio, and Ranorex.

Our organization is broken into separate sections and there is a team for installation and configuration that handled the deployment. As I am not part of that team, I am unable to judge the complexity of the setup.

My advice for anybody who is implementing this product is to make use of the extensive library that they have. It is a good collection of training videos and documentation, and I would advise everybody to go through these materials. They are really helpful and it will allow them to learn much faster, bringing them to the point where they can use it to its full potential.

In summary, I am really comfortable with this tool, I haven't had many problems, and it's sufficient for our work. In the three years that I have been working with it, whenever I've needed something, I've been able to find it.

I would rate this solution a nine out of ten.

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

• Scriptless tool -- great for those, like me, who don't have a lot of knowledge in coding to test software
• Works quickly and easily

I have worked a lot with Tosca for the past year, and it has helped our organization complete many tasks which most of the other tools couldn’t.

Being a scriptless tool was pretty helpful for me, as I don't have a great knowledge of coding. Its features helps us complete the work soon, and in an easy way.

It’s been one year I have been using this tool and it's been pretty good working with it.

5/5

5/5

It was easy, and a straightforward approach.

With it being a scriptless tool, it helps people without coding knowledge to work with ease.

The amazing features provided by Tricentis takes automation to a different world and it's fun working with it.

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.

This solution allows you to create an entire automated framework where it allows you to easily manage everything in one place.

It's given us the ability to do automated tests which has made some things a lot quicker.

A part of our problem is that we don’t necessarily have staff 100% dedicated to it, so that's a problem in our area. We should have had more done and taken on some huge projects, so it’s more that we haven’t had the time to use it to the greatest extent possible.

Our stability problems mentioned below notwithstanding, I am sure the new release will address everything that we need. We are going to convert to the new version and we have to address a problem with one of our apps first. We recently went through some training, our staff was excited about that and being able to see the new version was great.

The biggest roadblock for us in getting the newest version right now is accommodation of our application. The current version makes our lives easier, but we're still holding off on some testing until the accommodation issues has been resolved.

I've used it for a year and a half.

We've had no issues with deployment.

I think the version we're using is fairly stable, but I think the new version is not so stable, and that’s what's stopping us from moving over to it. We're having application problems, but once that's resolved, we'll move over to the new version.

It's scaled for our needs so far.

Overall, I'd say that technical support is good. When I have had interaction or problems, I let them know and they provide me with get instant feedback. I have been happy with that.

We didn't use a previous solution, but I've personally worked with other tools. Testsuite is versatile, and that was the big thing about choosing it. We're using Power Builder, which Testsuite can support, along with other applications. So it's great having one tool instead of many.

I think it’s important to get the training that is provided and really make sure you get hands-on time with the product. That’s our problem -- we haven’t been able to dedicate ourselves to it. If we had the time to stay with it and learn it then we could move forward.

We are using Tricentis Tosca for test automation.

Tricentis Tosca has completely met our requirements. It has benefitted our organization.

The most valuable features of Tricentis Tosca are all the test automation functionality. It is a full-scale automation tool.

I have been using Tricentis Tosca for over five years.

The stability of Tricentis Tosca is excellent.

We are using Tricentis Tosca at 100 percent capacity.

The support we received from Tricentis Tosca was good, but it can improve.

I rate the support from Tricentis Tosca a three out of five.

I rate the price of Tricentis Tosca a two out of five.

I rate Tricentis Tosca a nine 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.