In this four-part series QA Financial reviews the year that reshaped quality assurance in financial services, examining the forces that influenced testing, software risk management, and digital resilience. Part I can be found here. Tomorrow part III.
If Part 1 of this series explored how artificial intelligence has reshaped the direction of quality assurance in financial services, Part 2 focuses on the foundations that make that transformation possible.
Over the past year, QA-Financial.com reporting has consistently highlighted that AI-driven testing does not exist in isolation. Instead, it sits on top of a rapidly evolving stack of cloud infrastructure, data platforms, and resilience frameworks that are themselves becoming central QA concerns.
For QA and software testing teams in banks, 2025 has been defined by a widening quality mandate. Testing is no longer limited to applications. It now extends across cloud services, third-party ecosystems, data pipelines, and operational resilience capabilities, all under increasing regulatory scrutiny.
Cloud adoption in banking has moved decisively beyond experimentation. Throughout the past 12 months, QA Financial covered how major banks are scaling cloud-native platforms for core banking, payments, risk, and analytics workloads.
As these migrations accelerate, QA teams are confronting a reality in which traditional testing environments are no longer sufficient.
Testing in cloud-native architectures introduces variability that challenges conventional assumptions about stability and control. Infrastructure is ephemeral, services are loosely coupled, and releases occur continuously.
QA teams are therefore being pushed to design testing strategies that validate not only functionality but also the behaviour of systems under changing infrastructure conditions.
Testing must now account for auto-scaling, failover behaviour, service degradation, and latency patterns across regions and providers.
The news coverage has repeatedly emphasised that quality engineering in the cloud is inseparable from environment orchestration. Banks are investing heavily in test environments that mirror production as closely as possible, while also remaining cost-effective and compliant.
This has elevated the importance of infrastructure-as-code, environment provisioning automation, and observability tooling as part of the QA function. The ability to spin up realistic environments on demand, inject faults, and observe system behaviour has become a defining capability for mature QA organisations.
Test data management
Another dominant theme from the last year of reporting is the rising importance of data as a quality risk. As banks rely more heavily on analytics, AI models, and real-time decisioning, defects are increasingly caused not by broken code, but by flawed or poorly governed data.
Test data management has emerged as a critical bottleneck. Production-like data is essential for meaningful testing, yet regulatory constraints around privacy and data protection limit how real data can be used.
This tension has driven increased adoption of data masking, synthetic data generation, and automated data provisioning. QA teams are now expected to validate not just application logic, but also data lineage, transformations, and integrity across complex pipelines.
Reporting over the year has also shown that data quality issues often surface only at scale, under realistic loads and conditions.
As a result, performance testing and data validation are converging. QA teams are testing how systems behave when processing high-volume data streams, how data consistency is maintained across distributed systems, and how downstream services respond to delayed or corrupted inputs.
These scenarios are increasingly viewed as core quality risks rather than edge cases.
Perhaps the most consequential shift for QA teams in 2025 has been the elevation of operational resilience from an infrastructure concern to a core quality objective.
Regulatory regimes such as the EU’s Digital Operational Resilience Act have sharpened supervisory focus on how financial institutions prepare for, withstand, and recover from technology disruptions. QA Financial’s coverage has repeatedly underscored that testing is central to demonstrating resilience.
This has expanded the scope of QA into areas traditionally owned by operations and risk teams. Testing now includes scenario-based resilience assessments, validation of recovery time objectives, and assurance that critical services can continue under stress.
QA teams are being asked to simulate outages, third-party failures, and extreme transaction volumes, not as occasional exercises, but as part of continuous testing programmes.
The reporting also makes clear that regulators expect evidence. It is no longer sufficient to assert that systems are resilient. Institutions must show that they have tested failure scenarios, identified vulnerabilities, and implemented controls. This places QA teams at the heart of regulatory readiness, responsible for producing artefacts, metrics, and documentation that demonstrate resilience in practice.
Third-party risk
Another recurring theme from the past year is the growing complexity of third-party and vendor ecosystems. Cloud providers, SaaS platforms, fintech partners, and data vendors are deeply embedded in modern banking architectures. Our news site has highlighted how this dependency expands the testing perimeter far beyond systems directly controlled by banks.
QA teams are increasingly involved in validating third-party integrations, assessing service-level assumptions, and testing failover strategies when external services degrade or become unavailable.
This requires new forms of collaboration between QA, procurement, risk, and vendor management teams. Testing strategies must account for contractual obligations, shared responsibilities, and limited visibility into vendor internals.
Our news coverage also shows that banks are responding by formalising third-party testing requirements, including contractual expectations for testing support, incident data, and resilience evidence. QA functions play a key role in translating these requirements into practical test scenarios and assurance processes.
Moreover, throughout 2025, we reported on the convergence of performance engineering and traditional QA. As digital channels become the primary interface for customers and counterparties, performance issues are increasingly treated as quality defects with direct business impact.
Banks are investing in continuous performance testing, integrating load and stress tests into CI/CD pipelines rather than running them as isolated pre-release activities.
This shift reflects the reality that performance characteristics can change with every deployment, infrastructure update, or data growth pattern. QA teams are therefore being asked to provide ongoing visibility into performance trends, not just point-in-time assessments.
This convergence has also elevated the importance of observability. Logs, metrics, and traces are no longer just operational tools. They are becoming inputs into quality analysis, helping teams understand how systems behave in real-world conditions and how defects manifest over time.
Expanding skill set
Across the last 12 months, one of the clearest messages from our reporting is that the skill profile of QA professionals in financial services is changing rapidly.
Cloud literacy, data engineering awareness, and an understanding of resilience principles are now as important as traditional testing expertise.
QA teams are expected to work closely with platform engineers, security specialists, and risk managers. This requires a shared language and a deeper understanding of how systems are built and operated.
As testing shifts left and right across the lifecycle, QA professionals are becoming connectors between development, operations, and governance.
By the end of 2025, it is evident that cloud, data, and resilience are not separate initiatives but interconnected dimensions of quality.
QA teams that succeed are those that embrace this expanded mandate, evolving from application testers into quality engineers with enterprise-wide influence.
The news from the past year paints a picture of QA functions under pressure, but also gaining prominence. As banks continue to modernise, the ability to assure complex, cloud-based, data-driven systems has become a defining capability. QA is no longer about keeping pace with change. It is about enabling it safely, transparently, and sustainably.
As 2025 comes to an end, QA Financial reviews in this four-part series the year that reshaped quality assurance in financial services, examining the forces that influenced testing, software risk management, and digital resilience. Part I can be found here. Tomorrow part III.
COMING IN 2026
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
- Leapwork engineering head: Why test automation so often fails to deliver
- World Economic Forum warns financial sector must strengthen AI risk controls
- How Banca Progetto is hard-wiring quality into Italy’s digital banking space
- How Wealthsimple builds quality into the product, not around it
- Digital revamp puts spotlight on internal controls at China Construction Bank
WATCH NOW
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
