A test suite optimization approach that leverages symbolic classification, a greedy algorithm, and a similarity measure reduces MBT-generated test suites for embedded software by identifying and eliminating redundancy while minimizing its impact on the fault detection rate.
Abstract
Abstract The test suites generated through model-based testing (MBT) often include redundant test cases that neither enhance coverage nor fault detection but instead reduce test execution efficiency. Such test cases should be discarded to minimize the test suite size and its effect on execution cost while preserving fault detection capabilities. In this paper, we present a test suite optimization approach, implemented in a tool, that leverages symbolic classification, a greedy algorithm, and a similarity measure. It reduces MBT-generated test suites for embedded software by identifying and eliminating redundancy while minimizing its impact on the fault detection rate. We comparatively evaluate the optimized test suites against the original MBT-generated and also the manually created test suites, focusing on fault detection effectiveness and test execution efficiency. We also examine the robustness of proposed approach using two substantially different industrial case studies from Alstom Rail AB, Sweden. Results showed a significant reduction of over 80% in test suite size with a minimal effect on fault detection effectiveness. We further find that the test execution time of optimized test suites is equivalent to that of manually created ones, while achieving a fault detection rate ranging from 87% to 100%. Hence, results indicate the effectiveness and robustness of the proposed approach despite different redundancy sources (i.e., behavioral and structural) across the considered systems during the MBT test generation process.
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.