What is our primary use case?
From Tricentis, I have used Tosca for test automation and qTest for test management.
I use the solution in my company since many clients use SAP. Most of the clients have some SAP solutions with Fiori and SAP ECC. The last use case we did was on a client, so we are implementing Tosca for automated test cases and for rollouts in different countries. We had about 50,000 automated test cases.
What is most valuable?
The most valuable feature of the solution stems from the fact that it offers technology coverage because you can automate any technology, like in the mainframe, applications, client applications, or Word documents. I would say that we can automate the entire flow for endpoints where we work with such tools.
What needs improvement?
I would say the reporting part of the tool is an area of concern where improvements are required. I would say that extracting reports is a complicated process because it requires complex environments. At the client's end, when we have a small client, it is a little bit hard to deal with the reporting part. Sometimes, we have to export an Excel file. We can use all of the tool's integration features to extract, but most of the time, when Tricentis does not have all the environments, we need to export such stuff to Excel and work manually.
In the future, there should be some easy ways to export files in Tosca because it uses a specific key language, TQL, to export the data. We need some expert on TQL query language, as it is not very easy to use and export data. In the next release, I believe Tosca should have some user-friendly features.
For how long have I used the solution?
I have been using Tricentis Tosca for seven years. My company acts as a partner of the tool.
What do I think about the stability of the solution?
It is a stable solution. For all the bugs you have, you get good support from the vendor. I would say it is a stable tool. Sometimes, when you get some issues or some bugs, we contact the tool's support team quickly. In my opinion, it is a stable tool.
What do I think about the scalability of the solution?
It is a good and scalable solution.
The tool was not used globally, but around 700 people used it during the lockdown.
The tool is meant for big businesses.
How are customer service and support?
The solution's technical support has a maximum of two days of SLA. The first point is to contact the support team, and if they don't solve the issue, then you can schedule a live remote session to show the tool's support for the issue. I rate the technical support a ten out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
For some web applications and APIs, I use Selenium.
How was the initial setup?
The product's initial setup phase was easy.
The solution is deployed on the cloud services from Microsoft Azure, but sometimes, it could be AWS as well. I guess it is Azure because my company is also a Microsoft partner.
The solution's deployment does not take a long time. It takes two weeks to configure all the systems and consider the automation scope. The tool has many other features, and implementing everything takes a little bit more time. If you want to run Tosca on many machines in the cloud, you can configure the distributions and executions, which have many features. Tosca installation takes two weeks to start.
In terms of the implementation phase, the first thing is to implement a server machine and install Tosca Server because it offers services where you can set up other Tosca products, but there are licenses that need to be acquired by the vendor. The tool has a feature that is responsible for test data management. Looking inside Tosca, we have to create a framework when you start to work on the folder structure, how you keep the structure on the test case, and so on.
What was our ROI?
In the beginning of the purchase when you do assessment, the investment depends on the number of executions the client is planning. If there is a project you plan to roll out in many countries, it is a good approach to ensure some return of investment.
What's my experience with pricing, setup cost, and licensing?
The price of the tool is a problem for a lot of Brazilian clients or Latino clients, as it is expensive. Where I work, if one is low price and ten is high price, I rate the tool's price as a ten out of ten. Everybody here understands that it is a really expensive tool. My company also has some clients from the USA or Munich, and even if it is more expensive than the other tools, it is easier to sell the solution. Overall, I can rate the product price as a nine or ten because most of the clients are from Brazil.
What other advice do I have?
In terms of what has significantly improved test automation in Tricentis Tosca, I would say that it is traceability. In Tosca, we can trace the user cases and all the test cases to any extent. We can measure test coverage. From the user-front, it is easy to work with the tool.
Speaking about how the risk-based testing approach of Tosca impacts our clients' testing outcomes, I would say that when we start working on a client, we do some assessments to understand the maturity level of the client based on the past. Also, we work and provide some demo specials, show the features the tool has, and then provide some solutions.
Tosca is not very good for test management. Tricentis has some other tools, like qTest, which is a good option.
I recommend the tool to others.
I rate the tool a ten out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure