Why we chose to partner with Leapwork.
In a previous entry we went through Cinq Amis’ journey in becoming banking automation specialists. We gave an insight into all the spilled blood, sweat and tears, listed where we went wrong and finally recounted the things we learnt from this experience.
Part of our journey included choosing an automation tool which would complement our offering and be simple enough to handover to our clients after our work is completed. In this blog we go through the reasons why we chose to partner with Leapwork to deliver our clients a state of the art, fully automated testing system.
Which tools made the shortlist?
Our client’s needs were very specific: they wanted testing for their mortgage platform to be automated, end to end. The system ran across several products; from the customer facing portal, to the back office to the servicing system while also going through other touch points for things such as product loading, regulatory and compliance checks. The sheer scale of the system itself with over 15,000 data entry points spread across 200 products, meant we needed a tool which would greatly decrease the amount of time spent keying in an individual case.
Whilst speed was of the essence, there was also a need for the tool to provide stability and make for an easy handover once the project was finalised. It took us three months to find the right tool which would automate a Windows-based, complex DPR mortgage platform. The tools we trialled out were: Katalon, Ranorex, QTP, Selenium and Leapwork.
At this point we were already using Katalon but as with many open source tools it had limitations and we would have needed to deploy a range of other tools which would individually take care of different sections of the system. This wasn’t ideal as we wanted our clients to - in true Lord of the Rings style - have one tool to rule them all.
Next we looked at QTP, a tool we had used in the past and which we knew would work well with Windows-based systems. However, QTP has a complex structure which requires niche skills and is on the expensive side, so this too was eliminated. Ranorex was next, but we found it to be slow for the needs of this particular client, which left us with Selenium and Leapwork.
Selenium is a great tool and in fact forms the basis of Leapwork, however this is more suited towards developers rather than testers using automation. Had we gone with Selenium, there would have been higher costs needed to recruit developers with a different skill set. Selenium meant there was the need for more time to maintain the code. Additionally, human coding also leads to errors, so errors in the code and errors in the automation can lead to further issues.
This is when Leapwork saved the day. A “No Code” tool with the ability to allow the user to exercise their code knowledge should they wish to do so. Such a tool would also allow our client to be set up for the future without the need to hire extra developers.
The results we managed to achieve thanks to Leapwork
Leapwork does depend on having the right validation steps in place. Luckily, with our extensive testing backgrounds, this is our bread and butter so we were able to start transferring our framework from Katalon over to Leapwork and continue to develop the automation cases further. Once up and running, UAT cases were a breeze to set up, large amounts of data were quickly processed and we produced full regression packs in line with the functionality delivered.
When keying in a case would take between 25 to 40 minutes we were able to reduce this to just 4 minutes. An end to end case test would normally take around approx 90minutes, but after the implementation this was reduced to just 25 minutes. This is the true power of automation!
Apart from the speed, Leapwork helped us get to grip with the whole system. Implementing the full automation system through Leapwork also gave us the opportunity to have a complete overview of all tests carried out before something went live. If something does go live and it causes pain down the line, Leapwork lets you see if that process broke in any previous releases. If it didn’t, then something must have changed within the code. This means bugs can be traced back easily and you can better understand what went wrong and the way to fix it.
What can we offer you?
The hard work is now done. We’ve done end to end testing automation for other banking platforms and have been able to perfect our testing automation offering and condense it to 5 simple steps. Cinq Amis can guarantee a fully automated system within 6 months and at a fixed price.
If you are looking at implementing a comprehensive automation testing framework, which covers everything under one hood Cinq Amis is here to help. Get in touch on firstname.lastname@example.org.