Oct 2026· International Journal of Scientific Research in Science and Technology· 0 citations· 6 references
TL;DR
A transition from code-level defect metrics toward process- and system-level maintainability concerns is highlighted, and five research gaps are identified: separating testing practice from testing metrics, context-aware empirical design, standardized measurement and reporting, longitudinal maintainability tracking, and cross-domain replication.
Abstract
Automated testing is widely adopted in modern software development, yet empirical evidence on its relationship to software quality and maintainability remains fragmented across studies that differ in scope, metrics, and methodology. This focused structured review examines the development of automated-testing evidence from early defect-density and code-churn research to large-scale open-source mining studies, industry experiments, and systematic reviews of test-driven development (TDD). The review analyzes five foundational studies covering code churn, industrial TDD adoption, comparative automated-versus-manual testing, large-scale coverage analysis, and systematic synthesis of TDD quality effects. It then incorporates five recent studies extending this foundation toward industry experimentation, Kitchenham-protocol systematic review, practitioner-perceived technical debt, cross-domain validation in quantum software, and a meta-analysis of the reliability of existing TDD systematic reviews. The selected studies are analyzed according to their objectives, evidence source, methodology, evaluation outcomes, and limitations. The synthesis highlights a transition from code-level defect metrics toward process- and system-level maintainability concerns, and identifies five research gaps: separating testing practice from testing metrics, context-aware empirical design, standardized measurement and reporting, longitudinal maintainability tracking, and cross-domain replication. The review concludes by outlining corresponding future directions for evaluating automated testing's role in software quality and long-term maintainability.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.