Quickly identifying and fixing code changes that introduce regressions is critical to keep the
momentum on software development, especially in very large scale software repositories …

Growth in Google's code size and feature churn rate has seen increased reliance on
continuous integration (CI) and testing to maintain quality. Even with enormous resources …

Continuous integration promises advantages in large-scale software development by
enabling software development organizations to deliver new functions faster. However …

Developers rely on regression testing in their continuous integration (CI) environment to find
changes that introduce regression faults. While regression testing is widely practiced, it can …

Continuous Integration traditionally relies on testing every code commit with all impacted
tests. This practice requires considerable computational resources, which at Google scale …

Continuous integration (CI) systems perform the automated build, test execution, and
delivery of the software. CI can provide fast feedback on software changes, minimizing the …

Developers often address multiple development issues to make composite code changes,
as opposed to atomic changes that address one single issue. Investigating and testing such …

Developers expend significant effort on reviewing source code changes. Hence, the
comprehensibility of code changes directly affects development productivity. Our prior study …

At IVU Traffic Technologies, continuous integration (CI) pipelines build, analyze, and test the
code for inadvertent effects before pull requests are merged. However, compiling the entire …

Change-based testing is a key component of continuous integration at Facebook. However,
a large number of tests coupled with a high rate of changes committed to our monolithic …