Skip to content
Open access

Paired Code Smells and Test Smells: A Fine-Grained Longitudinal Empirical Study

Oct 2026 · Proceedings of the ACM on Software Engineering · Vol 3, pp. 3956 - 3978 · 0 citations · 57 references

TL;DR

A fine-grained longitudinal study on the co-evolutionary dynamics of "paired smells", which refer to cases where code and test smells exist concurrently in linked production and test code, and identifies 30 statistically significant rules where specific test smells imply the presence of underlying production code smells.

Abstract

As software systems grow in complexity, ensuring maintainability is essential, but often hindered by various quality issues. Among them, code smells and test smells are widely recognized indicators of technical debt that degrade system quality. While production code and test suites are intrinsically coupled and evolve together, existing research predominantly studies code smells and test smells in isolation, ignoring their underlying connection over time. To bridge this gap, this paper presents a fine-grained longitudinal study on the co-evolutionary dynamics of "paired smells", which refer to cases where code and test smells exist concurrently in linked production and test code. By analyzing 128,417 commits across 19 long-lived open-source Java repositories, we investigate the statistical associations, survival lifespans, and removal motivations of these paired flaws. As a result, we identify 30 statistically significant rules where specific test smells imply the presence of underlying production code smells and our survival analysis reveals that in most repositories, paired smells have relatively shorter lifespans than unpaired ones. To explain this phenomenon, our manual inspection reveals that paired smells often signal deeper structural issues, prompting explicit risk-driven refactoring. Finally, we discuss the implications of these results for code quality analysis and continuous integration tools, suggesting that they should link related smell findings between production and test code and guide synchronized refactoring.

Read PDF

Similar papers

Open access 2026

Fine-Tuning UniXcoder for Code Smell Detection in Java Projects

This study investigates the application of UniXcoder, a pre-trained transformer model for source code, to classify Java source code methods across multiple projects as smell or clean, with a particular focus on the Switch Statements smell, and confirms that pre-trained transformer models, particularly UniXcoder, are ca...

Hanson Prihantoro Putro, Umi Laili Yuhana, E. M. Yuniarno et al. · 0 citations
Book Open access Oct 2026

Prompts Matter: On the Impact of Code Smell Remediation with Large Language Models

Code smells accumulate as technical debt, reducing software maintainability. Refactoring is the established remediation practice, but it is complex and often deprioritized. Large Language Models can support automated refactoring, but their effectiveness depends on how they are prompted. In this study, we evaluate 14 pr...

Nadim Hagatulah, Markus Borg, E. Söderberg · 0 citations

On the Impact of Requirement Smells in LLM-Based Code Generation

The results suggest that increasing \textit{smell density} was generally associated with lower test-suite-based functional correctness, although non-smelly requirements could still produce faulty code, and motivates further investigation into task-dependent quality effects in LLM-assisted software engineering.

Hugo Villamizar, Jannik Fischbach, Mert Şahin et al. · 0 citations
Preprint Nov 2026

Finding the Pivots to Repair Broken Source-Test Evolution Using LLMs

This paper presents a systematic empirical study of test repair for source-test co-evolution empowered by LLMs, investigating the effective setups and typical LLM behaviors, and derives a common reasoning action taxonomy from LLMs'reasoning traces, which proves instrumental in guiding LLMs to repair tests more effectiv...

Xiao Chen, Song-Qiang Chen, Jia-Lun Cao et al. · 0 citations
Book Open access Oct 2026

KatalIA: Can a Declarative Metamodel Make LLM-Based Smell Characterization Traceable?

Software engineers need to identify and assess maintainability concerns in source code to support inspection and refactoring decisions. However, code-smell characterization is context-dependent: static-analysis tools such as SonarQube provide systematic rule-based findings, whereas LLMs offer contextual interpretation...

Diego Gatica, René Nöel · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.