Code smells are structural characteristics of software that may indicate a code or design
problem that makes software hard to evolve and maintain, and may trigger refactoring of …

Bad smells are sub-optimal code structures that may represent problems needing attention.
We conduct an extensive literature review on bad smells relying on a large body of …

Software repositories contain historical and valuable information about the overall
development of software systems. Mining software repositories (MSR) is nowadays …

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 …

Several code smell detection tools have been developed providing different results,
because smells can be subjectively interpreted, and hence detected, in different ways. In this …

Context: Code smells are assumed to indicate bad design that leads to less maintainable
code. However, this assumption has not been investigated in controlled studies with …

The metaphor of technical debt was introduced to express the trade off between productivity
and quality, ie, when developers take shortcuts or perform quick hacks. More recently, our …

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 …