Tricentis Tosca Initial Setup

NibsMishra
AVP, Testing Service Owner at a insurance company with 10,001+ employees
When we did the initial setup — and this is a lesson we learned as a company — it was not directly with Tricentis. We worked with one of our global service providers, Accenture. They are the ones who proposed some of these tools to us and they are the ones who helped with the initial setup. They were here with us for 2018. In 2019, we took it on from them, and then Tricentis came onboard and we started having a direct relationship with Tricentis. Looking back, I think it would have been much better if we had had a direct relationship with Tricentis from the get-go. There were some things that were done where Tricentis came in and said, "Hey, this is how you should have done this." That was a lesson learned for us as a company where, going forward, even if we have global service providers, we will hopefully have direct contact with the vendor as well. That's something we didn't do. We did take a complex area with COBOL and all that, so we needed customizations, but we did it through a GSP and it was okay. It went pretty well. I wouldn't say the setup was very complex since Accenture did the heavy handholding, so it was easy for us. Had we done it, it would have been a different story, but Accenture paved the way for us. For the initial setup, we had five or six folks from our side. Accenture's team was offshore but there were three or four of their team here. It was a pretty complex application. There were ten to 12 people who worked on it to get it going. Once the initial baseline was set, we had people automating it, working with business, coming up with the list of features, prioritizing the features, and then coming up with a roadmap. When we go into these waves, it's a nine-month plan. The first week is diagnostic where we consider which applications we even want to attempt to start automating. Then we do a two-week design period where we consider which flows we want to automate. What are the critical flows or critical business functionalities within the application, with the most manual testing or the most frequent testing, that we want to automate? We identify five workflows, usually critical and high-priority, that we will try to automate using Tosca. Then we have a one-month "test-and-learn" where two or three people from our side partner with the department testers, and they automate things during that a month. Once that's done, we provide a recommendation saying, "Hey, we did it. Tosca seems to be the better option. Here are the benefits you will get." There is then an operationalized phase of usually six, and up to nine, months after that. At the end of those six to nine months, we should be able to go from 36 people down to 20. We come out with a big plan that we present to the department. They all agree. We talk about what skillsets are needed going forward. How many will be flexible staff, how many will be contractors, how many will be associates? We replicate that plan every time we go to a business. That is a plan that Accenture helped us put together and it has been very successful. That's something which Tricentis is trying give over as an example to some of their bigger clients because it's been a pretty successful implementation so far. It is a reusable, repeatable process that we have come up with. Every group knows what to expect out of it. The learning curve for Tosca is not steep compared to some technical products. It has been pretty okay, as long as the people have the mindset. So when we hire quality engineers, we don't ask them questions about Tosca. We ask them questions about their mindset to see if they have an automation-first mindset. What we are seeing from a skillset perspective is that 80 percent of the manual testing quality engineers are able to make a shift but at a lower level. For entry-level or mid-level people, it's very easy to make the shift. At a higher level, we do expect our quality engineers to have some technical aptitude, like SQL programming skills. in addition to Tosca, we are also using Tosca BI, which needs SQL skills. So we do need some technical skills, but we are seeing much better success in transforming our manual testing population to using Tosca and Tosca BI than we have seen with any other development or programming language. So the learning curve is pretty good. It's easy and not too steep. We have been doing the implementation in a wave approach. We didn't go with a big-bang saying, "Okay, we want to implement Tosca everywhere," because that would not work. Instead, we did an enterprise-wide transformation. We looked at testing spend for each department and started with the ones that had the highest testing spend. We put together a two-and-half-year to three-year roadmap saying, "Here is how we are going to hit applications, the big applications." We have 40 major application suites, each of which can be a combination of applications. We defined roles, because each application suite needs an application suite quality engineer who is going to be accountable. We had a whole process that we worked through. It was not just a tool transformation but a transformation in terms of people and technology. Technology came at the end. It was more transforming peoples' mindsets and making sure they understood what we were trying to do. We wanted them to understand the intent because with Tosca, it's very easy to fall into the same trap as with anything else. If there are practices where people have wrong naming conventions or don't understand the value of versioning that Tosca provides, there is a need to create best practices. Tricentis has been pretty good at teaming up with us to share their best practices and working with us to come up with best practices that work for our company. View full review »
reviewer1215411
Global QA Manager at a financial services firm with 1,001-5,000 employees
On a scale of one to ten, with one being straightforward and ten being complex, the setup was around six or seven. It wasn't completely straightforward but it wasn't totally complex either. It just needed some insight from Tricentis to make sure things were being done correctly. The first deployment took about a week. We then went through an upgrade where we used their consulting service as well, because that was when they changed how the licensing was done and the license server. That took about two weeks to do. With this latest upgrade, we're going on our fifth week now. It's taken us a little longer because of that issue that we uncovered. Our implementation strategy was a global implementation, where we empowered all delivery teams to be able to use Tosca. We set up the application servers and the repository in a global data center and then we pushed out Tosca Commander to all the delivery teams so they could do test automation and manual testing as well. View full review »
gagneet
Continuous Delivery Lead at a tech consulting company with 1,001-5,000 employees
Setup is simple, but requires learning of the tool and how it does things, before you can optimally use it. 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
The initial setup is straightforward, provided that the consultants from the company are involved. View full review »
LaurentEsnault
Bid Manager - Expert Continuous Testing at Sogeti UK
The initial setup is very easy. Deployment took about half a day. If you want to deploy it on just the local machine, it will only take about ten minutes. However, if you want to deploy it to an environment with a common repository in a collaborative multi-user mode on a database that allows some concurrent shared work, it might take up to one day. View full review »
Robert Foerg
Project Manager at a logistics company with 5,001-10,000 employees
Setup wasn't that straightforward; it was more complex. It all depends on the environment, because there were a lot of errors on our applications. Therefore, it wasn't an easy setup for us. It took time to begin setting up for the first time because it's not a regular setup. It took us a week to set up. View full review »
Vaishali Mane
Practice head for Automation at a tech services company with 10,001+ employees
The upgrade I was involved in was complex. We had some issues with it. 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.