- Automation of regressive test cases
- Entering process and risk structures as basis for test design
- Entering logical test cases as basis for meaningful executable test cases
- Using the same test tool now as well for manual business testing
Improves the software quality in production by finding more defects with automated test sets, before transporting developments to production.
Reduces the effort for acceptance testing by business colleagues by
About 10 years.
Sometimes new features do not work as shown on slides, in the first release.
Not now. In previous versions yes, for more than 10,000 test cases.
Nine out of 10, and now further improving.Technical Support:
Eight out of 10. Sometimes too (ITIL) process focused and too little content focused.
We used, and still use, our test tools depending on the test focus. But we switch to Tosca whenever respective functionalities are stable, usable in our tests.
Recent upgrade went smoothly. Upgrades have gotten better over time.
Upgrades are done in-house, new features are done with vendor.
We have used Tosca for a long time now. Recent new projects on Tosca have a ROI between one and two years. The cost driver is less the tool than the project effort.
Start with a test version.
Start with a pilot project, have Tricentis or a partner support the setup, pilots and extensions.
Tricentis is very good in communicating and sharing test best practices and often ahead in offering new trends in development and testing.