Mauritius Commercial Bank (MCB), the oldest and largest bank in Mauritius and one of the leading financial institutions in sub-Saharan Africa, has taken a major step forward in its digital transformation journey.
Partnering with Temenos, a Swiss banking software company whose core platform underpins the operations of more than 3,000 financial institutions worldwide, MCB has overhauled its technology landscape to drive greater efficiency, agility, and automation.
For QA and testing teams across the global banking sector, the project offers a revealing case study in how large, regulated institutions can modernise their testing architecture without disrupting mission-critical operations.
At the heart of the transformation lies a dramatic improvement in automated testing, resulting in faster deployments, reduced workloads, and streamlined environment management.
Digital journey so far
MCB has long been on a path of transformation. The bank has used the Temenos Core platform since 2007 and more recently embarked on a major overhaul of its systems landscape, engaging Temenos and choosing a private-cloud, container-based architecture to support its digital banking ambitions.
In this latest chapter, the testing and QA function has become a critical enabler.
According to the published case study by Temenos, MCB achieved “at least 90% improvement in overall automation testing.”
It reduced the effort in creating new development environments from “around five days and the efforts of multiple teams” to “within a day.”
The bank estimated this resulted in “a 70% reduction in workloads” for its internal development teams. These figures signal a major shift in efficiency and test throughput for an institution operating in a regulated, high-availability banking environment.
MCB’s Architecture Chapter Lead, Reza Chady, described the bank’s motivation as rooted in a rapidly evolving operating environment.
“Innovation plays a very important role in our culture, and we pride ourselves on being able to adapt to a demanding operating environment,” he said.
Chady added that “today, customer preferences and regulatory requirements are evolving rapidly. To stay ahead of the change, we need banking systems that are flexible and adaptable, while also providing a secure environment for delivering our services.”
Equally, he said: “Our core banking landscape has not grown in a very uniform way. Previously, we maintained five different versions of Temenos Core, with individual environments for each operating entity. This approach was overly complex, and made it difficult to scale the business and execute new strategies in a unified way, not to mention adding considerable cost and management overheads.”
“Today, we’re deploying new services faster, with fewer issues. Before, it took around five days and the efforts of multiple teams.”
– Reza Chady
From a QA perspective, the consolidation of multiple core banking versions into a single instance not only reduces complexity but also inherently simplifies the testing matrix of versions and instances.
MCB’s move to a centralised technical stack in its private cloud, including the use of the Red Hat OpenShift Container Platform container architecture, supports modern DevOps and continuous-delivery practices by enabling faster environment spin-up and automated deployment.
As Chady noted: “Today, we’re deploying new services faster, with fewer issues during release management and more controlled access to production. Before, it took around five days and the efforts of multiple teams to create new development environments; now, we create them within a day. We estimate that this has resulted in a 70% reduction in workloads, and we expect to build on these efficiencies as we automate more workflows.”
He also emphasised the cost savings angle: “By migrating to Temenos Core in our private cloud, we expect to reduce our hardware estate by at least 70%.
Likewise, by consolidating from individual instances to a single core banking platform and database, we expect to realise significant savings on licensing costs, as well as administrative and maintenance resources.”
Key takeaways
For QA teams in banks and insurers, key takeaways from the MCB case include the strong linkage between core consolidation and testing simplification, the benefit of containerised architecture to rapidly create and manage test environments, and the quantifiable workloads and automation gains that can be communicated up the chain to business stakeholders.
MCB’s phased ‘low-risk’ upgrade approach also underscores a prudent QA strategy. Chady explained the first implementation phase.
“The initial upgrade took around six months to complete and went very smoothly. Since then, the latest version of Temenos Core has been working perfectly, as is the Red Hat OpenShift environment. The combination of Temenos and Red Hat has proved really powerful, and we are very pleased with the stability and performance we have achieved since the upgrade.”
Testing teams will recognise the value of such a phased roll-out in limiting scope, ensuring stability, and building confidence before broader rollout across subsidiaries.
MCB’s story illustrates that for banks in capital-intensive, highly regulated markets, achieving meaningful automation improvements is not simply a matter of adding tools, but of aligning core architecture, deployment strategy and environment provisioning with the QA agenda.
By reducing version fragmentation, enabling rapid environment creation, and embedding automation in the release process, MCB claims to have set a benchmark for QA maturity in banking.
As MCB continues to extend the new version of Temenos Core to regional affiliates and harness extensibility frameworks for payments and data-hub initiatives, its testing architecture will likely evolve further, Chady said.
THIS WEEK
Why not become a QA Financial subscriber?
It’s entirely FREE
* Receive our weekly newsletter every Wednesday * Get priority invitations to our Forum events *
REGULATION & COMPLIANCE
Looking for more news on regulations and compliance requirements driving developments in software quality engineering at financial firms? Visit our dedicated Regulation & Compliance page here.
READ MORE
- Inside JPMorgan’s $18bn QA push with OmniAI reshaping testing
- As AI takes hold, insurance firms face a new testing mandate
- K2view’s Amitai Richman calls out the ‘real bottleneck’ in healthcare and insurance
- AI in QA: how flexible testing is redefining assurance for financial firms
- Explainer: Why site reliability engineering is gaining momentum in banking
WATCH NOW
