I mostly use the TOSCA Commander to create test cases. I also utilize the Tbox feature to automate complex test scenarios. Lastly, I find the requirements linking very useful in analysis after a release (i.e. test coverage, etc.).
Technical Tester at a tech services company with 501-1,000 employees
Tbox automates complex test scenarios and it's helped us keep track of test execution and coverage.
Pros and Cons
- "The product is very useful in keeping track of test execution and coverage."
- "The product, at times, does not recognize objects, especially in web applications."
What is most valuable?
How has it helped my organization?
The product is very useful in keeping track of test execution and coverage. This is because it has a feature called Execution List which shows resources and the test cases they have executed. There is also a tab for Requirements where the test cases can be linked.
So, by combining those two together, you will be able to see which test cases are mapped to requirements, and if they have been executed. You will also see the number of passed and failed test cases. It is very easy to use once you know all the features. It barely crashes and recovers gracefully most of the time.
What needs improvement?
The product, at times, does not recognize objects, especially in web applications. It would be good to have that fixed in the next version. As a work around, you have to use the feature called TBox which allows you to scan complex objects.
For how long have I used the solution?
I have been using it for more than six months.
Buyer's Guide
Tricentis Tosca
February 2026
Learn what your peers think about Tricentis Tosca. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
885,264 professionals have used our research since 2012.
What was my experience with deployment of the solution?
No issues encountered.
What do I think about the stability of the solution?
No issues encountered.
What do I think about the scalability of the solution?
No issues encountered.
How was the initial setup?
The initial setup was hassle free. Although, it would be great if the documentation for the initial set up would include more screenshots and a troubleshooting section.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Software Analyst at a financial services firm with 1,001-5,000 employees
It's automated, allows us to design and integrate manual test cases, and we can see status and results in the requirements section.
Pros and Cons
- "We decided to go with Testsuite because you can integrate manual test cases and you can see the reports in a nice way and see how the test case is going in the requirement section."
- "With the license stability, we have had a lot of issues. There were many interruptions to the connection and it took two-three weeks and we installed the license ourselves."
What is most valuable?
- Test case design
- Shows results in the requirements section
- Manual test cases
- Automation
What needs improvement?
Test automation – how you can record the module. It’s already easier to record than it was, but there is still room for improvement.
UI has gotten better but could still be improved.
There are some keyword shortcuts in test case design and in general that could be introduced. Sometimes everything is too big – it’s hard to describe.
For how long have I used the solution?
I've used it for four years.
What was my experience with deployment of the solution?
Not so far because we only started automating now. So far we have not tried to move the existing project to a new version- we just started.
What do I think about the stability of the solution?
With the license stability, we have had a lot of issues. There were many interruptions to the connection and took two-three weeks and have installed the license ourselves.
What do I think about the scalability of the solution?
We just started – it should be ok.
How are customer service and technical support?
Customer Service:
Quite good – they were trying to solve the problem.
Technical Support:It was ok. I have seen better. They tried to find solutions quickly so that is a plus, and they always called back when there was an appointment or said they would call back.
Which solution did I use previously and why did I switch?
No previous version was used.
How was the initial setup?
Straightforward – only problem was with the license server.
Which other solutions did I evaluate?
We looked at Ranorex and Eggplant. We decided to go with Testsuite because you can integrate manual test cases and you can see the reports in a nice way and see how the test case is going in the requirement section.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Buyer's Guide
Tricentis Tosca
February 2026
Learn what your peers think about Tricentis Tosca. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
885,264 professionals have used our research since 2012.
Senior Test Manager, Head of Test Automation Process at a financial services firm with 1,001-5,000 employees
It accomplishes what a lot of different tools did before. We use it in our main, regressive, HTML, and web-case tests.
Pros and Cons
- "Testsuite accomplishes what a lot of different tools did before."
What is most valuable?
Business dynamic steering and table steering.
How has it helped my organization?
For example, you can make templates and share them with storage elements. We use it in our main, regressive, HTML, and web-case tests.
What needs improvement?
At the moment, none. In the latest version I don’t see much room for improvement.
For how long have I used the solution?
I've used it for six years.
What was my experience with deployment of the solution?
In the past there were.
What do I think about the stability of the solution?
The product is stable; no problems with stability features.
What do I think about the scalability of the solution?
We had in the past, but those are gone in the latest versions. In the beginning there were problems with scaling up, but those are gone as well.
How are customer service and technical support?
Customer Service:
We had QA Windrunner, which was running out of its maintenance lifecycle. Also, the product wasn’t very good as it caused problems, was only a tool for testing automation, and we needed a tool that could be used for several purposes like reporting, putting in requests, and data storage. Testsuite accomplishes what a lot of different tools did before. Now, three or so tools are no longer needed, and our testing is all unified in TOSCA.
Technical Support:It's very good.
Which solution did I use previously and why did I switch?
It's very good.
What about the implementation team?
It was implemented through a vendor team – our team members had done a TOSCA certification so they worked together.
What other advice do I have?
The best way to look into the solution, you have to experience things for yourself. Have technical support from the beginning so that you have guidance early on.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Test Manager with 501-1,000 employees
We're able to create reusable data classes when using our test cases, and non-technical testers can automate tests with access to information.
Pros and Cons
- "The primary driver for us is that it puts automation into the hands of non-technical testers."
- "So far, all our issues have had to do with our unfamiliarity with the product."
What is most valuable?
We like the idea of reusable data classes when we are using our test cases. We work with a lot of data, and so being able to create reusable data classes is very helpful to us.
How has it helped my organization?
The primary driver for us is that it puts automation into the hands of non-technical testers. Previous programs, if you’re not a programmer, you can forget about it, but with TOSCA it’s easier to get information and start automating your own tests.
What needs improvement?
So far, all our issues have had to do with our unfamiliarity with the product.
For how long have I used the solution?
We are in a preparation phase – we haven’t seen everything yet. We purchased it about six or seven months ago, and started actively creating tests in the last six weeks.
What was my experience with deployment of the solution?
No issues encountered.
What do I think about the stability of the solution?
No issues encountered.
What do I think about the scalability of the solution?
No issues encountered.
How are customer service and technical support?
Customer Service:
It's excellent, 9/10.
Technical Support:It’s excellent, 9/10, as the response times have been quick and there haven’t been any problems.
Which solution did I use previously and why did I switch?
Initial setup was straightforward. It took a little bit of juggling to get a central database set up as defaults to working in isolation, but other than that it was OK.
How was the initial setup?
We did it in-house.
Which other solutions did I evaluate?
TOSCA was recommended, so we didn’t look into anything else. Our software provider said it could support their solution so we went for it. We had looked into HP UFT and Smartbear. We had used HP UFT but are fading away from them.
What other advice do I have?
Be prepared to change how you approach test automation – definitely a mindset shift. It's highly configurable so you want to make good use of that. Don’t be afraid to ask for help from Tricentis, they will get back to you. Have a good bank balance because it’s not cheap.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Senior Manager of QA at a tech services company with 501-1,000 employees
Very rich automation/test management framework but consider the coding needed to integrate with your application
Recently, I was asked a set of questions regarding my experience with TOSCA. Here are the questions and my answers:
General info:
Is there any need for coding or scripting? Based on my research, I expect that the module is created when scanning has been finished. But some users commented that coding or scripting is needed.
- Depends on the application and technology you are trying to automate. TOSCA has a lot of engines (HTML, .NET, Java, Webservices, etc.) with control library's that can be used out of the box. For something that is not covered by these engines (like a custom java widget) you will need to code for steering.
Are control statements like if/then/else and loops supported?
- Loops are not directly supported. If/then/else are supported for templates (data driven test cases).
Test case organization:
Is it possible to group test steps and according to our needs include/exclude particular test groups?
- Yes
Is it possible to rearrange test steps once they are created?
- Yes
Is it possible to perform multiple execution for test steps and test groups?
- Yes
Is there a possibility to create some variables whose values can be adjusted in some of the test steps?
- Yes. In TOSCA variables are called "buffers"
Is possible to add references in a test to some other test?
- It's possible to organize test steps in the library and reuse them in TC's. For other kinds of references you are free to create custom fields (to store path to other TC for example).
Is it possible to modify verdicts, for example, if a test fails that is declared as passed?
- Yes
Is a test progress view supported? Is it possible to stop/start a test on an error or some other event?
- Yes. You can define different behavior on an error (for example requesting a manual action to continue).
Is it possible to schedule tests? This is useful to have when night runs are executed
- You can trigger TOSCA execution using the TOSCA API from cmd line using windows scheduled jobs.
When some test step fails in some test group, how is that reflected to the corresponding test group? Does the parent test group also fail?
- The parent test groups are organized as "Business execution lists". If one TC fails, Business execution list will also fail.
Logging:
Is it possible to filter results?
- Yes
How is logged data is stored?
- Execution results stored in a TOSCA repository (local or shared (DB))
Is it possible to export logs/results?
- Yes. You can print repository content to various formats (excel, PDF, jpg, etc.)
Other:
How does TOSCA work with the command line?
- The TOSCA API offers all operations in the cmd as the TOSCA Commander shell. Run TC's, Create TC's, print report, everything...
Is it possible to configure test speed? For example, to insert some delay when GUI is slow.
- Yes, there are multiple settings and options to play with the speed.
Is there any possibility to explore a linux system with TOSCA? Maybe via putty or WinSCP?
- I don't have experience with TOSCA and LInux. Theoretically TOSCA can run external applications. We have created integration of TOSCA and JUnit tests for our needs.
When a test is created on one system, can it be easily transferred to another system? For example, when I create a test, I want to deliver it to another colleague who is working on another machine. Or does he have to create it on his own machine?
- You can use multi-user repository, which has checkin/checkout operations like SVN or CVS. You can also export your TC's or other TOSCA objects to file and import to other local/shared repository.
In the end, what is your opinion/experience about TOSCA?
- Overall impression about TOSCA is quite positive - it's a very rich automation/test management framework. In the right hands it can be used for creation of a really powerful and complex solution. There are many more features that are useful for automation but there can really be a need for some coding effort to integrate with your application - this needs to be considered.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
My review was done for the older version of TOSCA.
Currently we work with version 8.4.0 and this tool has advanced a lot.
Tricentis added many useful features and TOSCA has become once of most mature automation tools I worked with.
If/then/else and loops supported, plugin for Continuous Integration exists now, JUnit test results can be imported into TOSCA, test data service allows to setup distributed execution, etc.
QA Expert at a tech services company with 51-200 employees
Good Visual representation, easy to understand and comfortable to implement business ideas
I have used TOSCA for R&D only,. not any real client project.
TOSCA is very good for
- Business requirement based test case not complex test scenarios
- Good Visual representation, easy to understand and comfortable to implement business ideas.
- Can cover only user validations. (you can not satisfy all possible complex scenarios and requirements)
- It is a good test case building tool for managers or business personnel not for a core QA person. So, if you are targeting for Technical QA career, it might not help that much. But, if you are on to business area, team lead who manage clients with requirements, it is very good tool for you.
- In market, it is not that much popular, so you may not get many jobs that need TOSCA
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
I started using the trial version of TOSCA Testsuite to get a first look at this software. I was impressed by the way how easy it is to create and execute test cases. I noticed that non-programmers can write test cases (no scripting required). This can be a con for testers because there are no loop statements and each test should be repeated many times. I also noticed that many adapters are supported out of the box, TOSCA Testsuite is fast, easy and intuitive to use and it has professional support.
QA Expert at a healthcare company with 501-1,000 employees
Great tool but I think it will take a few more years to mature & grow
After working on TOSCA for 18 months this is what I think:-
(Note: this is my personal opinion and not that of the company I work for)
There is no such thing as "No Coding skills required". Even TOSCA has some custom vb script files that come with the installation that allow you to do certain automation tasks. Also you can create your own vb script files and associate them to modules within TOSCA for further customisation.
My understanding of test automation is keeping your test scenarios in the centre and wrap your automation tool around it. TOSCA shakes this basic understanding of mine to the core. It's either the TOSCA way or the highway :)
I do not consider myself an expert TOSCA userit makes it easy simply because I do not know how to create custom controls in TOSCA (yet). May be future improvement in HELP files might help here.
The only benefit I have seen is the ease the maintenance of existing test automation scripts. Because the way TOSCA binds the tests with objects, test data sheet and so on when the time comes for maintenance it is really easy.
Concept wise - TOSCA is an great tool. A tool that promises no coding skills required. A tool that talks about moving away from conventional test automation methodology of object driven test automation towards model based test automation. But I think it is still a bit further away from reality and will take a few more years to mature & grow on its own.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Enterprise Resources Planning Specialist at Doyensys
Enables codeless automation and allows users to create test cases and reuse them
Pros and Cons
- "The product enables codeless automation."
- "It is quite difficult to integrate the solution with other tools."
What is most valuable?
Tosca is a good tool. The product enables codeless automation. If we need to write codes, it will take some time. With Tosca, we can scan things within a second, add the test, and run the script. We can track automation coverage with the help of requirements and coverage features. It is an effective feature. Reusable and library are key features of the product. Once we create the test cases with the help of the library and Reusable, we can call it repeatedly wherever we go.
What needs improvement?
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.
For how long have I used the solution?
I have been using the solution for one year and six months.
What do I think about the stability of the solution?
The tool is stable.
What do I think about the scalability of the solution?
The tool is scalable. We have 10 to 15 users.
How are customer service and support?
The support is good.
How would you rate customer service and support?
Positive
How was the initial setup?
We can easily install the product if we have the license. The deployment takes two to three weeks. We need one to two people for the deployment.
What's my experience with pricing, setup cost, and licensing?
The tool is quite expensive.
What other advice do I have?
Overall, I rate the solution an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Tricentis Tosca Report and get advice and tips from experienced pros
sharing their opinions.
Updated: February 2026
Product Categories
Functional Testing Tools Service Virtualization Mobile App Testing Tools Regression Testing Tools API Testing Tools Test Automation ToolsPopular Comparisons
OpenText Functional Testing
Katalon Studio
Apache JMeter
SmartBear TestComplete
BrowserStack
Postman Enterprise
Sauce Labs
Eggplant Test
Ranorex Studio
BlazeMeter
Selenium HQ
Perfecto
Worksoft Certify
UiPath Test Cloud
Buyer's Guide
Download our free Tricentis Tosca Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Tosca Testsuite Version 10.0
- Cost of TOSCA Testsuite?
- Is anyone using Tosca for Non Functional Testing?
- Does anyone know which CI/CD tools integrate with Tricentis Tosca?
- Looking for documents about TOSCA Testsuite
- What are the benefits of Tosca?
- Is Panaya Test Dynamix better than Tricentis Tosca?
- Tosca Testsuite with Selenium WebDriver
- How does Micro Focus UFT One compare to Tricentis Tosca?
- Do we require a separate license for DEX in Tosca?
















TBox is not a workaround. It's alternative engine to classic HTML engine.
Per my experience problems with Web automation are related with use of correct locators (IDs) and correct steering. Sometimes applications themselves are not automation friendly