Tricentis Tosca Reviews

We are using it for user names and login passwords. We are using model-based techniques where they have already entered IDs. Based on the ID, we can create the object, test case, test folder, and test types.

If I want to create a registration for five countries, I will create complete test cases and use the same data. There is no need to create different data or test cases for that. I can use the same data for different countries by using or passing the object from my object type.

In my previous company, I worked on two different projects. One was for the banking domain, and the other one was for the telecom domain. In both projects, I worked with web-based applications plus Windows-based applications by using Tricentis Tosca. I designed around 55 to 60 case designs in one project. I also worked on the test case design, maintenance, execution, delivery, and reporting. I wrote user stories and created some examples for test case stories.

The feature that I have found the most valuable is the recovery and cleanup process. Suppose there is a list of test cases and one test case has failed, it should not impact the other test cases. We can reuse the same test case. We can change the configuration of parameters and then use the test cases on the same thing. So, that's a useful thing. Otherwise, we have to use the cleanup process.

Another useful feature is to have our own library files. We can create our objects in the libraries and reuse them. There is no need to create duplicate data for that.

They have been giving some enhancements recently which means integration is also there. They've integrated with different software like Jenkins, Bamboo. So, we can also create pipeline points. They have recently given SAP and everything, which is very useful.

It would be of great help if they can fix the loading or performance issues. Sometimes, when I create the test case folder and test cases, it feels like it has loading or performance issues. When passing the objects, we can't sometimes find the exact element. We need to find out that exact location and just give the path for that, and then it works.

In the pipeline, when creating Jenkins, we create the list execution for passing the execution list to the commander. I feel it is a bit late, by a fraction of seconds. I first thought it could be my mistake or a setting issue, but I worked on that, and it's not a mistake or a setting issue.

I have been using Tricentis Tosca for around six plus years. 

Its stability is much better. Last time, it was 10 points, and now I feel it is 12 points. 

Tricentis Tosca is actually around 1.2 GB. It takes around 20 to 25 minutes for installation. 

We have different setup files, and we use Java for that. We use jar files for Java, and then we need to set the location and Tricentis Tosca home directory, for which we can set the variable path from environment variables.

I deployed it by myself. 

I am satisfied with the cost

I would definitely recommend this product to my colleagues or my friends because it is very useful if they are using the Tosca Query Language (TQL). We can find exact data from any project, which is one of the best benefits. It is a very easy, convenient product for everyone.

Tricentis Tosca is very easy to understand. We can reuse data, and no redundant data is required. I like this tool. I am also interested in self-learning this tool and its features. 

I would rate Tricentis Tosca an eight out of ten. It's very good performance-wise.

Tricentis Tosca is used to test our in-house products. We have developers for Google and other web applications for our internal use, but that product is developed by outsourced developers, that needs to be tested.

The most valuable feature is being able to create a test case by recording some scenarios and then leasing that task case to other scenarios.

We only use the UI for testing purposes, so all other features are unusable to us.

The document object model or some aspects of it has a bit of a learning curve.

I have been working with Tricentis Tosca for one year.

We use the latest version.

I don't have any issues with the stability of Tricentis Tosca.

Because my organization or team only has one or two testers, we don't need to think about scalability. As a result, that product does not need to be scalable in my environment.

My experience with the Tricentis website support was good.

I have experience with Selenium HQ and Parasoft.

We conducted a SOAtest using Parasoft. Tricentis Tosca is different and better, because it has a reusable model, whereas the others do not.

The initial setup requires some learning time. In my experience, we have testers who have no development experience, so we need to educate them on the development side. I'm referring to the ID in the document object model or some aspects of it. After that, we'll be able to use it. In my experience, the learning curve was the most difficult obstacle.

It took approximately three months to complete the deployment.

This solution is maintained by two people, the same two who use it.

I was able to learn the installation process myself.

Licensing fees are paid on a yearly basis.

I would recommend this solution to others, but in our country, I believe the importance of testing is currently ignored or underestimated. It is not popular in our country at this moment but I will recommend this tool.

We are partners with Tricentis.

I would rate Tricentis Tosca an eight out of ten.

Our primary use of the solution is for mocking of API codes.

One feature we like is the live connectivity of the product. In other words, you can push transactions through to live, and you can intercept some transactions and return them back with mocked data.

We haven't used the product extensively yet, so I don't have a specific area for improvement at this time. We could say customization could be improved.

I've been working with the solution for over one year.

The solution seems to be stable; from our usage level so far it is.

The initial setup was complex.

We did the setup ourselves, but we're bringing in an external company to help us understand better and be able to properly use it ourselves.

The pricing of the solution comes as part of our Tosca bundle, so we're happy with that.

I would rate the solution a seven out of ten. It needs additional support for industry-standard protocols.

My advice to anyone looking to implement this solution would be to bring in an expert to make sure that the initial setup is done correctly and then build upon that.

Tosca can work with a wide range of technological solutions. So Tosca is not just a replacement for open-source products. It's integrated with different technologies, desktop applications, package solutions like SAP, and mobile applications.

Right now, I can't think of any areas where Tosca can improve because we are not yet that experienced with delivering services based on Tosca.

I've been using Tosca for nearly three years.

We haven't implemented Tosca at a large enough scale to really comment on that. 

We haven't had any major problems with the product, but when we've had issues, Tricentis support has been generally responsive.

The implementation process is manageable and easy enough. It's an example of a good implementation approach.

Primarily I'm dealing with customers looking for a cheap solution, and they are willing to try open-source automation solutions. So from this perspective, the price of Tosca is not as competitive. And these alternatives are on the radar of larger companies that are investing in the delivery of their products. So Tosca is not penetrating the market as much because of the license prices.

I would rate Tosca eight out of 10. The only disadvantage is the high price. Still, I would say it's worth trying because the barrier is low to implement automation, and it works with a broad scope of technologies and applications.

We use Tricentis Tosca for testing.

The user management could improve in Tricentis Tosca because it is confusing. It would be better to have it in one place. Having to add it to the cloud and to a specific project can be a mess. 

In the future, they could improve overall mobile functionality.

I have been using this solution within the past 12 months.

The solution is stable. However, we had a situation with an application we wanted to test some reset passwords. We have the two-factor authentication enabled on sending an SMS to a number and in this case, we did not find anything to solve it. There was not anything to automate me getting the number, and proceed with it automatically without going and testing it manually.

The technical support is good, we were satisfied.

I have previously used Selenium in the company I used to work for and it was perfect. The solution was very good at testing web applications, but not Windows, or desktop applications. Tricentis Tosca does not have customized reporting tools ready but Selenium you can build and customize whatever you want.

Tricentis Tosca is an expensive solution and there is an annual license required. The whole licensing process is confusing and it could be made easier.

My advice is if companies have developers, or the potential to teach developers, or QA teams, I would suggest they use Selenium because the price of Tricentis Tosca is expensive.

I rate Tricentis Tosca an eight out of ten.

We are using this product for web UI testing, SAP, and API testing.

We are using a multi-user environment and the central repository gives everyone very easy access, which lets them re-use the models or whatever artifacts they need from other teams.

Apart from that, with the distributed execution, we are able to execute thousands of test cases in a very small amount of time.

These two things, I feel have been very helpful in my project.

I have found the test templates to be very useful.

Distributed execution with RDP is highly useful.

This solution is very easy to learn and any non-programmer or manual tester, with little experience in automation, can pick it up quite easily. 

It has a built-in repository to store all of the artifacts in the same place.

The inbuilt test datasheet that it has can be simplified and improved.

There are some performance challenges, specifically when we are not using it on a virtual machine, but when we are using it on a local machine.

In order to integrate test management tools, we have to buy another product call Tosca Connect. It would be better if this were included so that integration with tools like Jira or Azure DevOps was included out of the box.

One of the issues that we are facing is that the size of the repository continues increasing. They should provide tools to minimize or at least reduce the repository size.

I have been dealing with Tricentis Tosca for between two, and two and a half years.

Tricentis Tosca is very stable and we are using it extensively. We have people working in India, as well as in the US and Europe, so we use concurrent licensing. Most of the time, everything is being utilized.

It is pretty scalable because of the templates. We can have a single template expand into hundreds of test cases, so it is scalable. In my project, we have between 50 and 60 people how are using it.

The technical support is an area where Tricentis can improve. Many times when we have raised a ticket, we did not get an urgent response. There is a time lag between the process of raising the ticket and getting a final resolution. There is some resolution in the interim, but to receive a final resolution will usually take between two and three weeks.

I had to call technical support for one of the issues regarding a test data survey. We didn't have Microsoft Excel on our workstations so there was a question of how to upload the data. The final resolution for that issue took two to three weeks, or even longer.

I was not involved in the initial deployment, although I feel that the installation of it is simple. I am just not aware of how to configure the repository.

My understanding is that it's an expensive product, although I don't know the specifics with regards to pricing.

I was not involved in the decision-making process.

The biggest lesson that I have learned from using Tricentis Tosca is that for test automation, you are not required to be a programmer or very technical.

Overall, this is a good product and I definitely recommend it.

I would rate this solution an eight out of ten.

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

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.

Our primary use case is UI-based regression tests on Microsoft Windows.

Compared to the old tools, WinRunner and TestDirector by Mercury Interactive, it accelerated building, performing, and maintaining regression tests by a factor of approximately ten times.

This solution is easy to use for everybody, including those who are not IT-educated.

It allows for effective test management and an effective test case design.

The most valuable features are:

• Non-scripting test case building
• Test cases are easy to maintain
• Very good test case design module
• All of the features are well integrated into the suite

I would like to be able to manage different projects in one repository or have better data exchange between repositories.

I have been using Tricentis Tosca for ten years.

Prior to this solution, we used WinRunner and TestDirector by Mercury Interactive.

The performance with Tricentis Tosca is better.