In the future, I would like to see improvements in Tricentis Tosca regarding the integration of test management tools, as the current process is very complex; for example, integrating with Jira Xray presents challenges, and there is not an easiest solution available right now. In terms of additional features I would like to see in the future, the self-healing process in Tricentis Tosca has to improve compared to other tools, as its current self-healing capacity is not that good. The self-healing process should automatically handle any changes in web applications; for instance, if properties change inside the application, the tool should automatically take care of it, unlike other tools such as Mabl and TestComplete that have better self-healing capabilities.
Senior Software Engineer 2 at a tech services company with 51-200 employees
Real User
Top 10
Jul 15, 2025
In Tricentis Tosca, we need to capture the element each time. If they could implement an auto-heal feature, it would capture automatically by detecting it from the page. This would be a beneficial future enhancement.
The self-healing feature of Tricentis Tosca needs significant improvement. Currently, it is static and not dynamic. For example, if a button in an application changes, Tricentis Tosca should be smart enough to detect the change and still execute the script seamlessly. Improvements are needed to ensure it responds dynamically to changes in the application.
The Vision AI implementation works very slowly, affecting the speed of our work. The exploratory testing feature is not working for version 2023.1, which we are currently using. It would be beneficial for the Vision AI implementation to undergo improvements to enhance performance.
Sr Test Automation Architect at a tech services company with 501-1,000 employees
Real User
Top 5
Dec 23, 2024
Making it a sense-based tool for Windows-based applications is an improvement. When using it with iOS devices, I cannot start automation directly and must use a remote machine. This could be easier. Moving to a cloud-based application rather than a desktop one could improve Tosca, as well as enhancing mobile automation support.
From what I've seen with my colleagues who make the software selection, the prices for this software in Brazil are too expensive to be applied to anything but huge customers. I'm surprised because I was in charge of planning and control at the company before, when there was a manager there. Normally, the company has structural licenses that are based on the company they are selling to. I see that these companies cannot spend this money on Tricentis. I think Tosca is losing this type of market. They should have a different license policy for medium and small companies. The same happened in the past with SAP, which changed its policy and also made licenses for low.
Product quality has declined as it grows, and its updates aren't without fault. The process of resolving problems has slowed, and as it expands into other areas like NeoLoad and other testing tools, the product becomes more complicated. It used to be a small firm with a clear goal, but as it grows, the quality has been affected.
Senior Test Consultant at a agriculture with 51-200 employees
Consultant
Top 5
Aug 21, 2024
The issue is that even though the components are tightly integrated, object identification can be quite slow, sometimes taking five to ten seconds. This delay is noticeable in UFTA. Additionally, reading data from external Excel files might contribute to the slow performance, though it's difficult to measure this precisely as a parameter.
Associate Manager at a consultancy with 10,001+ employees
Real User
Top 10
Aug 2, 2024
One major area for the product's improvement is simplifying the synchronization process of test cases between Tricentis Tosca and Solution Manager. It has been a challenge and could be streamlined to enhance user experience.
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.
The product's database capacity should be increased. The product has certain shortcomings in cloud storage. From an improvement perspective, cloud storage must offer more features.
Senior Test Manager at a financial services firm with 10,001+ employees
Real User
Top 5
Apr 26, 2024
In two areas, the update process posed challenges. Firstly, updating the software is quite tricky. Recently, with the new version released in 2023, we encountered several issues with our scripts. Secondly, managing the flow for license management was complex, possibly due to the intricacies within our company. It was not easy to manage all the licenses smoothly.
I am facing issues integrating the tool with the qTest server. It is the only problem I have been facing for a long time. I am not able to troubleshoot the issue. It is quite difficult to integrate the solution with other tools.
The product needs to improve object identification. The identify with properties and anchor methods work perfectly, while the by-index and image methods may face challenges.
More and more artificial intelligence (AI) is coming in. So, some amount of AI to create natural language processing (NLP)-based test cases and manage defects would be very helpful. This is because the technologies have evolved in the last five to six months, so there is a potential opportunity there. For creating test scenarios, looking at defects, historical defects, and kind of putting in generative AI would add value.
I think the downside would be licensing costs which are very high. Other than that, when it comes to any new issues, the tool is not supporting some features in the application, and then the need for customization comes as a drawback. These customizations are expensive, and we have to pay for them. Also, for integration with other tools like ALM or Jira we have to buy a Tosca connect license which again utilizes Tasktop tool for the integration. Using Tasktop to carryout the integration with Tosca and ALM or Jira is very time consuming and any kind of maintenance or support needs someone from Tasktop to have a look
Tricentis Tosca could improve on the ease of use. There is a steep learning curve. The reporting section could be better and some of the new features could be simplified. Additionally, the user management of the client and the server are confusing. There should not be two.
Tax Fee QA Director at a financial services firm with 51-200 employees
Real User
Dec 9, 2021
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.
Tricentis Tosca offers model-based testing that supports both technical and non-technical users through a user-friendly interface, enabling scriptless automation and seamless integration with UI and non-UI applications.Tosca's modular approach enhances test maintenance and reuse while delivering comprehensive automation for diverse testing environments. Backed by risk-based testing and automated data management, it supports end-to-end testing across API, SAP, and desktop applications. Tosca's...
In the future, I would like to see improvements in Tricentis Tosca regarding the integration of test management tools, as the current process is very complex; for example, integrating with Jira Xray presents challenges, and there is not an easiest solution available right now. In terms of additional features I would like to see in the future, the self-healing process in Tricentis Tosca has to improve compared to other tools, as its current self-healing capacity is not that good. The self-healing process should automatically handle any changes in web applications; for instance, if properties change inside the application, the tool should automatically take care of it, unlike other tools such as Mabl and TestComplete that have better self-healing capabilities.
In Tricentis Tosca, we need to capture the element each time. If they could implement an auto-heal feature, it would capture automatically by detecting it from the page. This would be a beneficial future enhancement.
The self-healing feature of Tricentis Tosca needs significant improvement. Currently, it is static and not dynamic. For example, if a button in an application changes, Tricentis Tosca should be smart enough to detect the change and still execute the script seamlessly. Improvements are needed to ensure it responds dynamically to changes in the application.
The Vision AI implementation works very slowly, affecting the speed of our work. The exploratory testing feature is not working for version 2023.1, which we are currently using. It would be beneficial for the Vision AI implementation to undergo improvements to enhance performance.
Making it a sense-based tool for Windows-based applications is an improvement. When using it with iOS devices, I cannot start automation directly and must use a remote machine. This could be easier. Moving to a cloud-based application rather than a desktop one could improve Tosca, as well as enhancing mobile automation support.
From what I've seen with my colleagues who make the software selection, the prices for this software in Brazil are too expensive to be applied to anything but huge customers. I'm surprised because I was in charge of planning and control at the company before, when there was a manager there. Normally, the company has structural licenses that are based on the company they are selling to. I see that these companies cannot spend this money on Tricentis. I think Tosca is losing this type of market. They should have a different license policy for medium and small companies. The same happened in the past with SAP, which changed its policy and also made licenses for low.
Product quality has declined as it grows, and its updates aren't without fault. The process of resolving problems has slowed, and as it expands into other areas like NeoLoad and other testing tools, the product becomes more complicated. It used to be a small firm with a clear goal, but as it grows, the quality has been affected.
The issue is that even though the components are tightly integrated, object identification can be quite slow, sometimes taking five to ten seconds. This delay is noticeable in UFTA. Additionally, reading data from external Excel files might contribute to the slow performance, though it's difficult to measure this precisely as a parameter.
One major area for the product's improvement is simplifying the synchronization process of test cases between Tricentis Tosca and Solution Manager. It has been a challenge and could be streamlined to enhance user experience.
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.
Tricentis Tosca is expensive. It should improve the testing of legacy systems and interfaces.
We faced some hardships in implementing the solution because of integration.
I would like to see something in terms of AI capabilities.
The product's test case management functionality needs enhancement.
The product's database capacity should be increased. The product has certain shortcomings in cloud storage. From an improvement perspective, cloud storage must offer more features.
In two areas, the update process posed challenges. Firstly, updating the software is quite tricky. Recently, with the new version released in 2023, we encountered several issues with our scripts. Secondly, managing the flow for license management was complex, possibly due to the intricacies within our company. It was not easy to manage all the licenses smoothly.
I am facing issues integrating the tool with the qTest server. It is the only problem I have been facing for a long time. I am not able to troubleshoot the issue. It is quite difficult to integrate the solution with other tools.
The product needs to improve object identification. The identify with properties and anchor methods work perfectly, while the by-index and image methods may face challenges.
The solution is expensive compared to other tools in the market.
The tool lags in client-based applications. We have also encountered issues with the features in integrations.
More and more artificial intelligence (AI) is coming in. So, some amount of AI to create natural language processing (NLP)-based test cases and manage defects would be very helpful. This is because the technologies have evolved in the last five to six months, so there is a potential opportunity there. For creating test scenarios, looking at defects, historical defects, and kind of putting in generative AI would add value.
I think the downside would be licensing costs which are very high. Other than that, when it comes to any new issues, the tool is not supporting some features in the application, and then the need for customization comes as a drawback. These customizations are expensive, and we have to pay for them. Also, for integration with other tools like ALM or Jira we have to buy a Tosca connect license which again utilizes Tasktop tool for the integration. Using Tasktop to carryout the integration with Tosca and ALM or Jira is very time consuming and any kind of maintenance or support needs someone from Tasktop to have a look
Tricentis Tosca could improve on the ease of use. There is a steep learning curve. The reporting section could be better and some of the new features could be simplified. Additionally, the user management of the client and the server are confusing. There should not be two.
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.