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 …

Tests that fail inconsistently, without changes to the code under test, are described as flaky.
Flaky tests do not give a clear indication of the presence of software bugs and thus limit the …

The adoption of agile approaches has put an increased emphasis on testing, resulting in
extensive test suites. These suites include a large number of tests, in which developers …

Flaky tests are software tests that exhibit a seemingly random outcome (pass or fail) despite
exercising unchanged code. In this work, we examine the perceptions of software …

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

Flaky tests are tests whose outcomes are non-deterministic. Despite the recent research
activity on this topic, no effort has been made on understanding the vocabulary of flaky tests …

Jupyter notebooks---documents that contain live code, equations, visualizations, and
narrative text---now are among the most popular means to compute, present, discuss and …

Code smells can compromise software quality in the long term by inducing technical debt.
For this reason, many approaches aimed at identifying these design flaws have been …

The impact of bad programming practices, such as code smells, in production code has
been the focus of numerous studies in software engineering. Like production code, unit tests …

Modern version control systems, eg, GitHub, include bug tracking mechanisms that
developers can use to highlight the presence of bugs. This is done by means of bug reports …