Regression testing is an essential activity to assure that software code changes do not
adversely affect existing functionalities. With the wide adoption of Continuous Integration …

Abstract Context: Continuous Integration (CI) environments allow frequent integration of
software changes, making software evolution more rapid and cost-effective. In such …

Automatic static analysis tools (ASATs) are instruments that support code quality
assessment by automatically detecting defects and design issues. Despite their popularity …

Developers often run tests to check that their latest changes to a code repository did not
break any previously working functionality. Ideally, any new test failures would indicate …

Continuous Integration (CI) has become a best practice of modern software development.
Yet, at present, we have a shortfall of insight into the testing practices that are common in CI …

Continuous Integration (CI) aims at supporting developers in integrating code changes
constantly and quickly through an automated build process. However, the build process is …

Benchmarks of bugs are essential to empirically evaluate automatic program repair tools. In
this paper, we present BEARS, a project for collecting and storing bugs into an extensible …

Continuous Integration (CI) has become a disruptive innovation in software development:
with proper tool support and adoption, positive effects have been demonstrated for pull …

Continuous Integration (CI) significantly reduces integration problems, speeds up
development time, and shortens release time. However, it also introduces new challenges …

The way developers edit day-to-day code tends to be repetitive, often using existing code
elements. Many researchers have tried to automate repetitive code changes by learning …