A Leading European Retail Bank Subsidiary Ensures a Highly Responsive Digital Experience for its 2M Customers With Specialized Quality Engineering

About Our Client

Our client is a subsidiary of a leading European retail bank with an unrivaled distribution network in the UK, serving close to 2M customers. They offer a portfolio of mortgage, savings, and loan financial products through local partnerships.

The Business Need

The retail bank embarked on a multi-year restructuring program to transform its UK operations into an agile, efficient entity with a reduced cost base. Under this program, the organization consolidated systems, streamlined back office processes of its Loan and Savings product lines, and simplified customer journeys.

The new operating model covered more than 40 functional and system-level integrations with the loans and savings product lines. They wanted to ensure that applications perform as expected even with bandwidth constraints, as well as:

Trigent Solution

Investing in continuous testing services was essential as the client consolidated 40+ systems and integrations across product lines. The unified solution required every change to be comprehensively validated across systems and processes. Trigent’s team, with over 25 years of industry and technical experience, expedited the design and setup of the Test framework in the pre-production environment.

Specialized quality engineering with performance testing

The Trigent team created a web application test suite to validate the customer portals. Besides Functional Testing, non-Functional Tests verified response time, throughput error rate, CPU, and memory usage. Performance tests, such as smoke, benchmark, iterative load, stress, endurance, spike, and volume tests, were done to assess end-to-end application responsiveness. The development team would alter the design and hardware configuration based on the dry-run results.

API performance testing strategy ensured the proper functioning of the programming interfaces.SIT, and UAT environments were used for test execution. A series of iterative tests for varying loads were conducted, and the team generated interim performance reports encapsulating:

• Summary of the test runs
• Key findings
• Measurable success criteria of each test

The technical stack

• JMeter- was used to execute performance tests and to create automated performance test scripts for critical scenarios.
• Light House GTMetrix-was used for webpage analysis.
• Bitbucket-was the tool for maintaining the source code.
• New Relic monitoring tool-was leveraged for monitoring servers (application and database).
• Grafana integration-was done for Integrations visual dashboards
• Jenkins integration-was done for CI/CD performance scripts.