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 …

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 …

Context Smells in software systems impair software quality and make them hard to maintain
and evolve. The software engineering community has explored various dimensions …

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 …

Practitioners use infrastructure as code (IaC) scripts to provision servers and development
environments. While developing IaC scripts, practitioners may inadvertently introduce …

Previous studies have investigated the reasons behind refactoring operations performed by
developers, and proposed methods and tools to recommend refactorings based on quality …

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 …