Tricentis Tosca Previous Solutions

NibsMishra
AVP, Testing Service Owner at a insurance company with 10,001+ employees
In terms of model-based, scriptless automation, Tosca is the first of its kind in our organization. We have been using Ruby Cucumber and Selenium, but they are all solutions where development and coding skills are needed. This is our first model/scriptless tool. We have an automation solution which was primarily Ruby Cucumber, but Ruby requires development skills. We had not been able to penetrate it into all the places we wanted it to be used. We have a lot of legacy and mainframe applications and there was a lot of downward testing still going on. On the digital applications and the go-forward applications, we have a good footprint from a Ruby perspective and test automation. But in all these legacy applications and some of the older technology applications, we had manual testing going on. We had a big goal as a company. We had done some benchmarking studies and what came out from them was that we are pretty good from a quality perspective when compared to our peers, but we are very expensive. So we were charged with a couple of things: to bring down the expense and increase speed, while maintaining the quality if not improving the quality. That's what led us on the path to Tricentis Tosca. When using Ruby, there are more hands-on coding development skills. Tosca is something that needs a technical mindset or aptitude, but even our manual testers were able to make the shift from manual testing to automation using Tosca. That was a big driver: How do we move from manual testing to more automation and how do we not impact the big workforce that we had in manual testing? We did not want to have to let go of all manual testers, and we didn't have enough skills from a Ruby perspective. With this effort, we have been successfully able to convert around 80 percent of our manual testers to automators, using Tosca. There are areas in our company which have Ruby, some of the digital areas, where it works. So we are letting those areas stay with Ruby. View full review »
reviewer1215411
Global QA Manager at a financial services firm with 1,001-5,000 employees
We used Selenium before Tosca. One of the reasons we decided to look at other tools was that, with Selenium, the maintenance of the scripts started becoming higher. The more and more that test cases were built, the higher the maintenance cost was and we started seeing a diminishing return as a result. Also, you really can't do database testing, for the most part. There are ways around that limitation, but it just doesn't work very well with Selenium. From a reporting standpoint, you really can't produce robust reports like you can within Tosca. Finally, the infrastructure with Selenium is a little bit more challenging and there's really no built-in test management with Selenium as well. View full review »
gagneet
Continuous Delivery Lead at a tech consulting company with 1,001-5,000 employees
Yes, have been using HP QTP and Selenium for Test Automation. Switch was mainly due to Team constraints and management wanting to try a new tool which is easier for the Business Analysts also to collaborate with. View full review »
Find out what your peers are saying about Tricentis, Micro Focus, SeleniumHQ and others in Functional Testing Tools. Updated: February 2020.
397,082 professionals have used our research since 2012.
Manish Kum@r
Senior Technical Automation Specialist at a consultancy with 51-200 employees
I was using Selenium WebDriver a few years ago. I switched to Tricentis Tosca because of its methodology and support for more than one hundred technologies. View full review »
Ulrich Becker
QA at a tech services company with 11-50 employees
Prior to this solution, we used WinRunner and TestDirector by Mercury Interactive. The performance with Tricentis Tosca is better. View full review »
Find out what your peers are saying about Tricentis, Micro Focus, SeleniumHQ and others in Functional Testing Tools. Updated: February 2020.
397,082 professionals have used our research since 2012.