Skip to content
Review Open access

THE EVOLUTION OF TEST AUTOMATION IN HIGH REGULATORY CRITICALITY FINANCIAL ENVIRONMENTS: A SYSTEMATIC LITERATURE REVIEW

Jul 2026 · Journal of Interdisciplinary Debates · 0 citations · 6 references

TL;DR

Test automation in regulated financial contexts goes beyond operational efficiency; it constitutes a risk governance mechanism that must be embedded in quality architectures from system inception.

Abstract

Context: The accelerating digitization of the financial sector, combined with increasingly stringent regulatory requirements, particularly the PCI DSS 4.0.1 standard, has created an environment where software quality transcends technical excellence and encompasses legal compliance and large-scale data protection. Objective: This systematic literature review (SLR) synthesizes the state of the art on test automation in financial systems with high regulatory criticality, examining dominant frameworks, strategies for integrating with CI/CD pipelines, and measurable impacts on pre-production defect reduction. Method: Following the PRISMA protocol, we searched IEEE Xplore, ACM Digital Library, Scopus, Web of Science, and SpringerLink for publications from 2015 to 2024. After applying inclusion/exclusion criteria and conducting a critical quality appraisal, 47 primary studies were selected for qualitative and quantitative synthesis. Results: Cypress and Selenium lead adoption in regulated financial environments, with Cypress demonstrating significant advantages in asynchronous execution stability and evidence traceability. Organizations implementing automated test suites integrated into CI/CD pipelines reported average reductions of 63% in defects escaping to production and a 47% acceleration in delivery time. PCI DSS 4.0.1 compliance emerges as a critical driver requiring dedicated test extensions for encryption, access control, and log traceability. Conclusion: Test automation in regulated financial contexts goes beyond operational efficiency; it constitutes a risk governance mechanism that must be embedded in quality architectures from system inception.

Read PDF

Similar papers

Jul 2026

Quality Assurance and Scalability: The Role of High-Test Coverage in Continuous Integration and Deployment Pipelines

The concept of productive coverage is formulated, shifting the center of gravity from gross quantitative test indicators to their semantic significance for business-critical scenarios, and practical recommendations are proposed for reconfiguring CI pipelines in order to minimize economic losses caused by brittle tests.

Evgenii Lvov · 0 citations
Jul 2026

Engineering Compliant Enterprise Systems: Architectural Constraints and Quality Practices in Regulated Industries

Successful delivery in high-stakes environments requires organizations to achieve a regulated operational state before project commencement, and treating compliance as a late-stage validation phase leads to significant technical debt and project failure.

O. Orlov · 0 citations
Open access 2026

TESTING AND QUALITY ASSURANCE (QA) IN LIBRARY SOFTWARE: STRATEGIES FOR RELIABLE RELEASES

Library software is at the crossroads of complex domain knowledge, diverse data, and varying user needs. It is imperative that the integrated library system, discovery system, digital repository, or interlibrary loan system maintains high levels of correctness, availability, and usability (Decan, Mens, & Constantinou, 2019). Introducing new features or making enhancements to existing functionality entails considerable risk, such as corrupted bibliographic data, broken circulation functionality, reduced relevance of discovery, or compromised patron privacy. Hence, it is imperative that we perform rigorous testing and follow good quality assurance practices to ensure the quality of the software release. Quality assurance for library software begins with the acknowledgment of the unique characteristics of the domain. MARC21, UNIMARC, and linked data formats are just a few of the bibliographic data standards that require stringent data representation and transformation. Interoperability with external systems, such as authentication services, discovery systems, payment processors, and consortium networks, provides ample room for integration defects. Legacy modules are also common in library software, and periodic batch operations are often required for data normalization, migration, and reporting. QA needs to ensure not just the quality of the software, but also the integrity of the data, data schema migration, and backward compatibility.

Samuel Osaretin Uwaifo (PhD) · 0 citations
Review

Clean Architecture in Modern Software Development: Ally or Villain?

It was concluded that Clean Architecture cannot be viewed solely as an ally or a villain, as its effectiveness depends on project characteristics, team experience, and the proportionate application of its principles.

Unknown authors · 0 citations
Open access 2026

Sustainable Compliance in Regulated Manufacturing: Deploying a Low-Code, AI-Driven eDHR Framework for Scalable Traceability

The deployment of a validated, low-code electronic Device History Record system on a high-mix, low-volume manufacturing line at Smith & Nephew’s Memphis site provides a practical and replicable model for regulated manufacturing environments that need to strengthen compliance while gaining flexibility for future analytics and system integration.

Pareshkumar Hotchandani, Mr. Wakhare · 0 citations