Jul 2026· International Journal of Modern Computer Science and IT Innovations· 0 citations
TL;DR
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.
Abstract
At present, the contradiction between the speed of delivering changes and the operational stability of software systems acts as a fundamental constraint for DevOps practices. In this study, the subject of analysis is the decisive significance of a high level of test coverage in continuous integration and delivery (CI/CD) pipelines, with a particular emphasis on how microservice architectural patterns determine the scalability of verification processes. The study relies on a mixed methodology that combines quantitative processing of metrics from the State of DevOps 2024–2025 (DORA) reports and the SonarQube State of Code with qualitative analysis of industrial cases from Netflix, Uber, and Meituan. It is demonstrated that although high test coverage (above 80%) is a necessary but not sufficient condition for reducing defect density, in the context of hyperscalable distributed systems it turns into a critical bottleneck in the absence of shift-right strategies, including automated canary analysis (ACA). A separate section is devoted to the 2024 Paradox of Engineering Productivity, where the introduction of AI assistants accelerated the generation of software code but simultaneously led to a 7,2% decrease in delivery stability. In conclusion, 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.
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.
Ricardo Polanski Alves· Journal of Interdisciplinary...· 0 citations
The monograph explores the key contradiction of modern software engineering: the conflict between the speed of delivery of functionality and the need to ensure the quality of complex systems. Based on the analysis of the evolution of QA practices, the systemic gaps of existing approaches to optimizing regression testing, such as impact analysis of changes (TIA) and methods based on machine learning (ML), are demonstrated. The author's methodology, Adaptive Quality and Test Impact (AQTI) Framework, is proposed as a solution. The scientific novelty of the framework is the integration of signals of the impact of changes in the code with a multifactorial assessment of the quality of the tests themselves, including their stability and business criticality. AQTI is formalized in the form of a transparent scoring model and an algorithm that allows you to create a minimally sufficient set of tests within the specified time constraints (SLA) with a guaranteed safety net of critical checks. The results of the retrospective modeling confirm that the framework is able to significantly reduce the time of test cycles while maintaining a high level of defect detection.
The monograph is addressed to researchers, engineers and architects. Due to its reliance on universal engineering artifacts, the proposed approach has not only theoretical but also practical value, being applicable in industries such as fintech, e-commerce and government systems.
Microservice-based systems evolve continuously through API changes, service splits and merges, dependency churn, and deployment-topology drift driven by DevOps practices. This rapid evolution erodes the assumptions encoded in formal models, test suites, and architectural descriptions, leaving practitioners with limited guidance on how to keep verification artifacts aligned with evolving implementations. Prior surveys cover microservices design, deployment, performance, and isolated verification techniques, but, to our knowledge, none consolidate the intersection of evolution and formal/rigorous verification, nor map how repository-derived signals and CI/CD pipelines support continuous verification of microservice-based systems. This paper addresses that gap through a systematic literature review (SLR). Following the Kitchenham et al. guidelines and PRISMA-style reporting, we defined a review protocol with four research questions covering (i) formal modeling and verification approaches, (ii) the impact of architectural and API evolution on verifiability, (iii) repository-derived signals for updating formal artifacts, and (iv) continuous and incremental verification in CI/CD pipelines. Structured searches in IEEE Xplore, ACM Digital Library, SpringerLink, and Scopus returned 1187 records, which were screened in seven stages and reduced to 18 included studies (13 primary studies that supply evidence and five background studies retained for transparency and framing) through inclusion/exclusion criteria and a weighted 15-item quality-assessment instrument. We synthesized the included studies thematically and compared them along five dimensions: verification technique, evolution dimension, automation level, empirical evidence, and tool/artifact availability. The synthesis shows that actor-based model checking, TLA+ control-plane verification, static code analysis, continuous certification, and runtime/self-adaptive testing form five complementary clusters, but empirical evaluation is dominated by small academic case studies, only a minority of approaches automate model updates from repository signals, and few are integrated end-to-end into CI/CD. We discuss methodological limitations of the body of work, including a lack of industrial-scale validation and shared datasets, contrast intrinsic (build-time, model-driven) and extrinsic (recovery-based) verification strategies, and outline a research agenda toward repository-aware, pipeline-integrated verification for evolving microservices. The present synthesis distils a set of immediate, evidence-based actions for practitioners together with a focused agenda of open research challenges.
R. Gómez, Ebeid Elsayed, Enrique R. Zarate et al.· Software· 0 citations
A comprehensive framework for integrating Load & Performance Testing and Security Testing into the software development lifecycle of enterprise-grade applications is presented, addressing scalability bottlenecks, throughput degradation under concurrent load, and security vulnerabilities that emerge specifically under high-traffic conditions.
Urvish Gajjar, H. Shah· International Journal Of Eng...· 0 citations
The rapid expansion of the life cycle for software deployment has required a move from traditional, manual security analysis to automated and integrated assurance frameworks. This study examines the effectiveness of integrating assurance, real-time threat detection, and automated certification gates right into the Continuous Integration and Continuous Deployment pipeline. The analysis is based on a synthetic dataset comprising values from 429 different builds, which is used to study the agreement between automated gating mechanisms and lower vulnerability escape rates. We used a standard tool chain consisting of Jenkins for orchestration, SonarQube for static analysis, and Splunk for log aggregation to emulate a high-velocity enterprise environment. The system seeks to reduce technical debt and potential security risks without impeding deployment velocity by enforcing stringent quality gates that prevent non-compliant artifacts from being promoted. The study highlights the quantitative effects of these controls on success build rates and on the exposure of hidden threats during staging. The results reveal that, despite an initial slowdown in delivery velocity, the incorporation of automated certification gates considerably reduces critical severity incident rates. Implications: The results indicate how to make system changes in response to data for those attempting to put DevSecOps into practice while maintaining the speed and integrity of their systems.
Sauhard Bhatt, Satyanarayana Gadiraju· 2026 6th International Confe...· 0 citations
VNVSpec, an open-source framework that makes V&V specifications machine-readable and executable, is introduced, which can handle up to 10,000 requirements and is evaluated by self-application, in which it is continuously assessed in CI against its own specification.
M. Arief, Nur Ahmad Khatim, Ali Akarma et al.· 0 citations