Banco Santander, one of Europe’s largest banks, is claiming to be rewriting the rulebook for how global financial institutions build, test, and deploy mission-critical software.
With more than 160 million customers and operations spanning Europe, the Americas, and Asia, the Spanish lender has completed one of the most ambitious technology transformations in banking: moving its entire core technology infrastructure in Spain to the cloud through its in-house platform, Gravity.
This milestone marks a turning point not just for Santander but may also for QA and software testing teams across the financial sector.
As banks modernise legacy cores and embrace real-time, API-driven architectures, the question is no longer if to automate testing, but how to test continuously, safely, and at scale in a cloud-native world.
Santander’s Gravity deployment offers a powerful example of how testing and resilience are being re-engineered for the age of digital banking.
In June of this year, Santander announced that it had migrated all its core technology infrastructure in Spain to Gravity, its in-house cloud-based core banking platform.
With the implementation of Gravity, Santander claims to become “the first major established bank in the Western world to operate 100 per cent in the cloud.”
The bank explained that Gravity “provides easier and faster access to data, shortens the launch time for new functionalities from weeks to hours, and enables more frequent app updates.”
In doing so, Santander España said it now able to handle 4.3 billion transactions per year, with peaks of up to 33,000 transactions per second.
That feat is not merely a migration, it is a transformation of the bank’s software test and release posture. By shifting its core banking logic into a cloud-native environment, Santander is reshaping where, when, and how QA teams validate change, stability, and risk.
The new architecture sharply reduces the friction between development and operations, and implicitly demands that testing practices evolve to match.
Strategic ambitions
Santander’s leadership is explicit about the strategic ambition. Ignacio Juliá, the CEO of Santander España, said: “The deployment of Gravity in Santander España marks a decisive step in the execution of our transformation, as we continue to make headway with other initiatives to evolve our operating model.”
Meanwhile, Dirk Marzluf, the group’s chief operating and technology officer, added that “Gravity makes Santander a ‘digital native’ company, with the agility and capability to provide the best customer experience and the security we’ve always offered. We are getting closer to fulfilling Santander’s vision of becoming the best open platform for financial services.”
For QA and testing teams inside banks, several key implications emerge from Santander’s journey.
First, testing regimes must scale with cloud velocity. As Gravity enables shorter launch cycle, ‘from weeks to hours’ as the bank claimed, QA teams will need to embed automated validation deeply into delivery pipelines.
Regression suites, data consistency checks, API contract tests, and performance soak tests must execute across each microservice or module as new code meets production-like environments. Traditional release windows may collapse; testing becomes continuous.
Second, the shift to cloud-native core banking also raises the bar on test data strategy. To validate edge-case behaviours, reconciliations, settlement flows, and financial logic, QA will need synthetic, masked, or generated data that mirror real transaction distributions and risk conditions.
Santander’s narrative emphasises that Gravity allows for ‘easier and faster access to data’, which implies underlying data services must be stable, consistent, and testable across environments.
Third, while Santander’s statements do not explicitly describe AI-driven testing, its architectural choices are consistent with an eventual adoption of model-based or anomaly-detection validations.
A cloud platform that supports versioning, telemetry, and observability offers the foundation on which AI-based test stability checks, drift detection, or predictive failure modelling could be overlaid.
Santander has long signalled that Gravity is not a project, but a strategic pillar across markets. The bank expects to migrate around 80 per cent of its core technology infrastructure globally onto the platform.
In certain business segments, such as its Corporate & Investment Banking arm, the bank already uses Gravity to host operations on Google Cloud, managing high volumes of accounting and treasury processing daily.
Before this, Santander’s technology leadership had made clear how central automation and cloud adoption are to its future.
The global CIO, David Chaos, asserted that more than 90 per cent of its IT infrastructure worldwide has already been migrated to cloud, and that core banking modernisation is underway with Gravity as its engine.
In his words, “every day, we are learning in this endeavour,” and the bank intends to complete the transition in its core markets within the next two to three years.
To QA and software testing professionals in banking, Santander’s journey offers a few lessons of forward relevance. Automating validation across a platform as sensitive as core banking demands rigour, traceability, and observability.
The move toward cloud-native operations gives testers access to infrastructure-driven verifications, such as autoscaling under load, distributed latency profiles and failure injection, allowing resilience testing that was much harder in monolithic architectures.
Santander’s shift also suggests that QA teams must be ready to evolve test types over time. What begins as API and UI automation may grow into anomaly detection, behavioural monitoring, or self-healing test flows. And importantly, the QA function needs to be embedded in platform decisions, not retrofitted afterward.
The deployment of Gravity in Spain may be the most visible milestone today, but the real scrutiny will come in how reliably it delivers over time.
For QA and testing teams in banks and financial services, Santander’s approach provides a timely case study: testing is not a gate, it must become the scaffold on which banking transforms into a digital-first, resilience-driven institution.
QA FINANCIAL PODCASTS
Listen to Sudeepta Guchhait on Nasdaq’s new Mimic AI testing platform
QA Financial sits down with Sudeepta Guchhait, Senior Director of Product Framework & Quality Engineering at Nasdaq
——–
Listen to Wesley Scheffel and Robin Rain on Schroders’ DevOps strategy
We catch up with Wesley Scheffel, Head of Cloud Platform and Product Engineering at Schroders, and Robin Rain, Head of Cloud Platform Architecture
——–
Listen to Citi’s Jason Morris on Lightspeed and the future of continuous delivery
Jason Morris, Head of Developer Pipelines for Securities Markets and Banking at Citi, talks about Lightspeed
IN LESS THAN TWO WEEKS
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
