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 …

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 …

In theory,(good) documentation is an invaluable asset to any software project, as it helps
stakeholders to use, understand, maintain, and evolve a system. In practice, however …

Code smells are poor implementation choices applied by developers during software
evolution that often lead to critical flaws or failure. Much in the same way, community smells …

Code smells represent poor implementation choices performed by developers when
enhancing source code. Their negative impact on source code maintainability and …

Background: Software vulnerabilities are weaknesses in source code that might be exploited
to cause harm or loss. Previous work has proposed a number of automated machine …

Software vulnerabilities are weaknesses in source code that can be potentially exploited to
cause loss or harm. While researchers have been devising a number of methods to deal …

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 …