Customer story · Banking
A test strategy for a new lending product, built into every sprint
From no test strategy to risk-based coverage, regression tests in every sprint, and a complete handover to the bank's own QA team.
- Client
- A Swiss bank for private clients and small businesses
- Where
- Switzerland
Challenge
The starting point
The bank was building a new lending product, a credit application, at a fast pace. There was no plan for how it would be tested, and they brought us in to set one up and run it.
- No QA strategy for the project, so testing was reactive and coverage uneven.
- No structured way to capture bugs while the product moved fast, which made them hard to prioritise, reproduce and fix.
- No test automation and no plan for it, so everything was tested by hand, which slowed every cycle and added risk.
Approach
What we did
Tools
- Tricentis Tosca
- Postman
- Jira
- A test strategy covering exploratory testing, bug management and test automation.
- Tricentis Tosca and Postman brought into the testing and automation, including the product's REST API.
- A regression suite that runs, and gets acted on, in every sprint, as part of development rather than an afterthought.
- Continuous integration and delivery set up with the bank's development partners, with testing running continuously alongside.
Results
What changed
- High coverage in the riskiest, most business-critical areas, so high-impact bugs rarely reached production.
- Testing and automation fully part of the sprints, with test cases written alongside the features.
- A complete, documented handover of the process, the tools and the automation framework to the bank's internal QA team.
Facing something similar?
Tell us about your team and what you're working on. One of our engineers will get back to you.