Continuous Integration (CI) is a popular practice in modern software engineering.
Unfortunately, it is also a high-cost practice—Google and Mozilla estimate their CI systems …

A long continuous integration (CI) build forces developers to wait for CI feedback before
starting subsequent development activities, leading to time wasted. In addition to a variety of …

Abstract Context Continuous Integration (CI) is a resource intensive, widely used industry
practice. The two most commonly used heuristics to reduce the number of builds are either …

Continuous integration at scale is costly but essential to software development. Various test
optimization techniques including test selection and prioritization aim to reduce the cost …

A Bug Inducing Commit (BIC) is a commit that introduces a software bug into the codebase.
Knowing the relevant BIC for a given bug can provide valuable information for debugging as …

In Continuous Integration (CI), accurate build prediction is crucial for minimizing
development costs and enhancing efficiency. However, existing build prediction methods …

The effectiveness of software testing is crucial for successful software releases, and various
test optimization techniques aim to enhance this process by reducing the number of test …

When a change introduces a bug into a large software repository, there is often a delay
between when the change is committed and when bug is detected. This is true even when …

Moving testing to the Cloud overcomes time/resource constraints by leveraging an unlimited
and elastic infrastructure, especially for testing levels like End-to-End (E2E) that require a …

Continuous Integration (CI) is a widely adopted process in software engineering that virtually
merges developers' pull requests with the code base to perform builds and tests essential for …