Metraipolis › archive › dc_8035c883e623

Is Self-Admitted Technical Debt Tested? An Empirical Study of Coverage, Co-change, and Impact — arXiv:2609.13485

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.13485
License (as archived)
CC0-1.0
Archived
2026-10-16T00:31:00.546Z
SHA-256 of the archived text
32ce49c39ae236ed6d662861dc3dcf0b2a72a518a0fc6c9fc88d2e2111769d29
Stable URL of this page
https://metraipolis.com/documento/dc_8035c883e623

How to cite

Is Self-Admitted Technical Debt Tested? An Empirical Study of Coverage, Co-change, and Impact — arXiv:2609.13485 — arXiv (en), https://arxiv.org/abs/2609.13485 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_8035c883e623 (Metraipolis archive dc_8035c883e623, sha256 32ce49c39ae236ed6d662861dc3dcf0b2a72a518a0fc6c9fc88d2e2111769d29)
BibTeX
@misc{dc8035c883e623,
  title = {Is Self-Admitted Technical Debt Tested? An Empirical Study of Coverage, Co-change, and Impact — arXiv:2609.13485},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.13485},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_8035c883e623; sha256 32ce49c39ae236ed6d662861dc3dcf0b2a72a518a0fc6c9fc88d2e2111769d29},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.13485. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

When developers write a TODO or FIXME comment, they are explicitly admitting that the code is suboptimal: a built-in warning that this logic deserves extra scrutiny. Yet it is an open question whether Self-Admitted Technical Debt (SATD) actually receives that scrutiny in the form of software testing. We aim to characterize the relationship between SATD and testing across three dimensions: the extent to which SATD-affected code is covered by existing tests, whether developers synchronize test additions with debt resolution, and whether such testing affects the long-term observability of resulting defects. For that, we conducted an empirical study on eight open-source Java projects, analyzing test coverage of 784 SATD instances identified in the latest releases and performing a longitudinal examination of 5,175 SATD removal events. Our results show that while 60.7% of SATD-affected code is covered by existing test suites, developers rarely synchronize test modifications with debt resolution; manual inspection confirms that only 3.4% of SATD removal commits include new tests specifically targeting the resolved debt (vs. 12.5% that co-add tests in the same commit). Longitudinal analysis further suggests that SATD resolutions exhibit nearly identical localized bug induction rates within short-to-medium-term windows regardless of test modifications. However, over a longer, unrestricted observation window, a slight divergence emerges where the test-added group reaches a higher cumulative defect alignment probability (6.32% vs. 4.37%), a counterintuitive trend potentially driven by the selective testing of inherently complex components. Developers treat SATD repayment as an ordinary code change rather than as a high-risk maintenance activity: most debt removals proceed without targeted verification, despite the developer's own prior flag that the code is suboptimal.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-15 in cs.SE).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2609.13485 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-16T00:12:31.091Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-15?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).