Oct 2026· Lecture notes in computer science· 4 references
Software Testing and Debugging Techniques
Abstract
Manual execution of website end-to-end (E2E) test cases is a repetitive, labour-intensive process that creates bottlenecks in modern software development workflows. We investigate the feasibility of automating this process using AutoQA-MAS, a large language model (LLM)-based multi-agent system (MAS) comprising four specialised agents coordinated through a shared data pool: a Web Agent that interprets natural language test cases and interacts with the browser via Document Object Model (DOM) analysis; a Vision Agent that inspects screenshots and agent context for visual defects; an Accessibility Agent that audits Web Content Accessibility Guidelines (WCAG) 2.1 Level AA compliance; and a Report Agent that semantically deduplicates findings into a consolidated quality assurance (QA) report. The system was evaluated across 90 test case executions on a controlled e-commerce environment, 89 of which produced valid reports, comparing OpenAI GPT-5-mini, Google Gemini 2.5 Flash, and Anthropic Claude Sonnet 4.6. The system achieved an overall goal completion rate of 85.4%, bug recall of 76.9%, and accessibility issue precision of 76.0% (GPT-5-mini and Gemini only), with Claude Sonnet 4.6 achieving the highest bug detection performance (91.5% precision, 84.3% recall, 87.9% F1) while consuming 28% fewer tokens than GPT-5-mini. We observe that well-defined detection criteria, such as WCAG standards, yield significantly higher precision than loosely scoped bug detection (76.0% vs. 65.9%), motivating richer contextual prompting as a key direction for improvement. These results demonstrate the viability of LLM-based MAS for autonomous web QA, offering a scalable pathway to reduce manual testing effort, lower quality assurance costs, and accelerate software delivery cycles without proportional increases in engineering headcount.
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
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…