Tricentis Tosca Reviews

We primarily use this solution in a 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 nine 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.

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

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

We had an in-house implementation.

We have seen 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. My 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.

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

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

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

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

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