Regression testing in continuous integration (CI) helps preserve delivered software value by exposing regressions early, but limited feedback windows make test order consequential. This study evaluates a leakage-safe dynamic test case prioritization framework that reconstructs job–build–commit provenance, combines strictly prior-build history with change–test similarity, applies class-conditional conformal calibration, and evaluates an operator-level deep Q-network (DQN). The primary held-out evaluation contains 273 failure-bearing jobs and 45,774 job–test rows from four Java projects. Pretrained history–semantic fusion achieved an equal-project macro failing-test-entity APFD surrogate (FTE-APFD surrogate) of 0.8840, compared with 0.8689 for history-only and 0.7023 for pretrained semantic-only ranking; the fusion–history difference did not survive Holm correction. A train-only TF–IDF control reached 0.7502 for semantic-only ranking and 0.8871 when fused with history in a seed-averaged diagnostic, so the benchmark does not establish unique superiority of the pretrained representation. A protocol-aligned RETECS reimplementation achieved 0.8296 ± 0.0111 FTE-APFD surrogate across five seeds. Adaptive conformal calibration reduced the candidate fraction from 0.3171 to 0.2598 while retaining 0.9058 failing-test coverage. The candidate-informed gated DQN remained below strong deterministic fusion rankings at 10%, 25%, and 50% budgets; five-seed, short-budget, hyperparameter, pre-execution-budget, and project-exclusion sensitivities did not establish a consistent DQN advantage. An additional three-project operational analysis containing 444 passing test jobs showed high failing-row coverage but strongly project-dependent candidate burden. Overall, the evidence favors strong leakage-safe deterministic rankings with explicit uncertainty control, while the evaluated reinforcement-learning design remains a local negative result rather than a general conclusion about reinforcement learning.
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
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.
MIT News · Artificial Intelligence· news.mit.eduSep 9, 2026
A weeklong summer workshop brought higher education faculty to campus to explore how AI and machine learning materials can be adapted for their classrooms.