Banks Get Head Start through Test Automation
June 6, 2017
In part 1, we revisited the business value for automated testing. In part 2 of this three-part series, we address the burning question of how to get started.
How does an enterprise get a head start with test automation?
“Implementing test automation must factor in the corporate culture of the adopting organization: its current processes, systems, and pain points.”Haidee Lim, Project Manager – Pointwest Banking and Retail Markets
One of the most compelling benefits when adopting test automation is the opportunity to inject a mindset of quality assurance across the organization. By “shifting QA to the left”, or as close to software creation and development, businesses minimize the cost of fixing defects to the lowest level, while increasing their responsiveness in attaining customer satisfaction.
To enable clients to get a head start with test automation, Pointwest offers enterprises a period of due diligence when it consults with clients to learn about the organization’s processes, current technology, and most importantly, culture and aspirations. Depending on the firm’s readiness to adopt test automation, due diligence could even bookend a proof-of-concept phase where test automation is implemented at a small scale, and a steady-state period where QA activities are actively co-managed with the client.
For enterprises that do not have a formal QA practice, this yields a smoother transition into automated testing as a managed service. For banks whose systems are intertwined with mainframes that run on legacy software, this fosters more successful adoption of the practice. Test automation on the mainframe is not an oxymoron; after all, tools exist that enable automated mainframe testing.
“What is essential before applying test automation, as with any technology tool or technique, is that it factors in the organizational culture and does not force one methodology over another,” Ms. Lim relates, “because buy in and support from stakeholders are crucial in successfully implementing change in an organization.”
Be it Waterfall, Iterative, or Agile methodology, test solutions can be customized and automated, which include:
- Test Design
- Test case design and creation
- API testing
- System testing
- Security testing
- User Acceptance Testing or UAT
- Pre-deployment testing
Another key consideration for a successful implementation is choosing a reliable and well-designed test automation framework. A robust framework means test engineers who have little to zero knowledge in automation can still implement. In addition, a scalable design offers flexibility to accommodate both current and future demands of the industry, including changing regulatory standards.
For example, Blockchain technology enables settlements and clearing to be automated across the financial sector, the significant savings of which can be passed on to the banking public. But as Morgan Stanley reports, adoption is gradual because it requires concerted effort from industry consortia, even as challenges in governance, cross-border regulation, and security persist. To make the test framework future-ready, the framework development team must have domain expertise, apart from strong software architecture and development skills.
Finally, to deliver expected results, test automation frameworks need monitoring, maintenance, modifications, and even upgrades.
The last installment of this three-part article aims to showcase the benefits of what continuous integration and deployment (CI/CD) can bring to test automation implementations.
Founded in 2003 by pioneers of the Philippine Global Sourcing industry, Pointwest creates value for its list of satisfied clients — including top Fortune 100 and local companies — with world-class IT and BPM services backed by international-standards methodologies and innovative practices.