Understanding Self-Admitted Technical Debt in Test Code: An Empirical Study
Ibuki Nakamura, Yutaro Kashiwa, Bin Lin, Hajimu Iida

TL;DR
This empirical study investigates the presence, types, and implications of Self-Admitted Technical Debt in test code, revealing its distribution, categorization, and the effectiveness of machine learning models for automatic classification.
Contribution
It fills the research gap by analyzing SATD in test code, proposing new categories, and developing a CodeBERT-based model for automatic classification of SATD comments.
Findings
SATD is prevalent in test code but not linked to test smells.
New categories of SATD types in test code are identified.
CodeBERT model outperforms others in classifying SATD comments.
Abstract
Developers often opt for easier but non-optimal implementation to meet deadlines or create rapid prototypes, leading to additional effort known as technical debt to improve the code later. Oftentimes, developers explicitly document the technical debt in code comments, referred to as Self-Admitted Technical Debt (SATD). Numerous researchers have investigated the impact of SATD on different aspects of software quality and development processes. However, most of these studies focus on SATD in production code, often overlooking SATD in the test code or assuming that it shares similar characteristics with SATD in production code. In fact, a significant amount of SATD is also present in the test code, with many instances not fitting into existing categories for the production code. This study aims to fill this gap and disclose the nature of SATD in the test code by examining its distribution…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
