Tricentis Tosca Reviews

Automating SAP and NON SAP applications 

Reduced Integration testing time effectively from 2 weeks to 1 day for CRM application.

With code free automation concept, it's easy to automate and maintain test scripts. Many of my team members shifted over the past two years, and upskilling and knowledge transition was never a problem. 

In today's agile and cloud world when solution and functionality are not stable, automation scripts' maintenance was not a big issue. Looking at the amount of rework and maintenance activity that we had done for our scripts, it might have been a nightmare with some other scripting tool.

They can make it more stable. I have used this tool for SAP applications. Tricentis's alliance with SAP mostly worked fine, but there were very few glitches. However, we got the required support from the Tricentis team.

They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack.

I have used this solution for more than one and a half years.

I scaled it up a few months ago, and it was not a smooth process.

I have worked on QTP/UFT and  SAP TAO for SAP automation. Considering no-code automation, easy maintenance, and integration capabilities with 150 + applications, I selected TOSCA for an automation solution.

Its initial setup is not very complex and needs the required skills/knowledge. It also depends on the environment. It is good to have a TOSCA expert in your team to support integration activities.

We engaged the SI partner for Tosca set up and automation.

We did not fully utilize its integration with the test management tool, but it was working fine. 

My recommendation would be to go through Tricentis documentation and the best practices that they are proposing. Wherever required, set up a knowledge-sharing session with Tricentis. 

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

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 have been using this solution in my organization. There are several clients who have come back to us asking for different automation tools and our views on which automation tools can be used in their respective projects.

We have been evaluating for these clients. The evaluations we were doing, was for our client but done within the organization only.

The most valuable feature is the UI.

We work primarily on evaluating the UI. We evaluated Tosca BI and a bit for Tosca APIs and think they are very useful.

The reporting is really nice. There are many clients who ask for a feature with any automation tool that can generate good reports for them. There is only one such tool that facilitates that option, which is Tosca.

The volume for the BI testing is limited. If they could provide a few options to use it, using Tosca only, that could be a great thing because there are a lot of clients who do not actually want to go for the BI, but then they do have the database testing.

I know that Tosca provides the feature but it's very minuscule.

The UI does not have the option of automating the scroll bars. There are workarounds for that but for example, if I open two tabs that have the same page then it will give me another difficulty in scanning those options. 

In the next release, including this in Tricentis would be great.

I have been acquainted with this solution for approximately eight months.

So far, what we have used has been stable.

I have read some reviews where they have expressed that they are not happy with the stability, but so far, I have not faced any such issues.

The scalability is good. If I had to rate it out of five, I would say that it would be a three-point five to four.

We have anywhere from 500 to 750 people who are using this solution in our organization.

Technical support is good. Their turnaround time is usually within 24 to 48 hours, but normally we have a response within 24 hours.

Previously, we did not work with any other solution.

We have always worked with the demo licenses, which included support from the Tricentis teams. They have always been able to set up the licensing.

I would say that it is not that straightforward.

On average, it did not take more than two to three hours if you know the process properly. To get it started, it will require at least six hours.

The disadvantage is that it is very expensive.

I would like to see better costing packs. There are several features but USD $11,000 for one license is expensive. If it had more interaction and if the license cost was a little less it would be better and rate higher.

The recommendation of this solution depends from client to client and what their requirements would be, the parameters, and what is important to them. 

If the client wants good support and at the same time they want to have a good database included with the Automation Testing Suite, and is ready to spend the money, then we would definitely suggest Tricenta Tosca as a good option.

Again, it is dependant on the client's requirements and what they would want in an automation tool.

If you have Linux or Mac machines, then it gets very difficult to implement Tosca. I would suggest using it. 

For testing, they would want to migrate miscellaneous scripts and use Tosca for those migrations. But, it's very difficult. 

My suggestion would be to go with the Tricentis Suites and the Selenium Automation Suites.

From a positive perspective, I would want people to use the reporting from Tosca. They have very good reporting. The reporting feature is very user-friendly and very easy to use.

I would rate Tricenta 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.