Background: Code smells indicate suboptimal design or implementation choices in the
source code that often lead it to be more change-and fault-prone. Researchers defined …

Code smells are symptoms of poor design and implementation choices weighing heavily on
the quality of produced source code. During the last decades several code smell detection …

Code smells were defined as symptoms of poor design choices applied by programmers
during the development of a software project [2]. They might hinder the comprehensibility …

In past and recent years, the issues related to managing technical debt received significant
attention by researchers from both industry and academia. There are several factors that …

Technical debt is a metaphor introduced by Cunningham to indicate “not quite right code
which we postpone making it right”. One noticeable symptom of technical debt is …

Code smells are symptoms of poor design and implementation choices that may hinder
code comprehension, and possibly increase changeand fault-proneness. While most of the …

In the last decade several catalogues have been defined to characterize bad code smells,
ie, symptoms of poor design and implementation choices. On top of such catalogues …

Test smells are sub-optimal design choices in the implementation of test code. As reported
by recent studies, their presence might not only negatively affect the comprehension of test …

Code smells are a well-known metaphor to describe symptoms of code decay or other
issues with code quality which can lead to a variety of maintenance problems. Even though …

Test smells have been defined as poorly designed tests and, as reported by recent empirical
studies, their presence may negatively affect comprehension and maintenance of test suites …