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 …

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

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 …

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 …

Software defects cost time and money to diagnose and fix. Consequently, developers use a
variety of techniques to avoid introducing defects into their systems. However, these …

Testing is an integral part of release engineering and continuous integration. In theory, a
failed test on a build indicates a problem that should be fixed and the build should not be …

Regression testing is used to check the correctness of evolving software. With the adoption
of Agile development methodology, the number of tests and software revisions has …

As software evolves, problematic changes can significantly degrade software performance,
ie, introducing performance regression. Performance regression testing is an effective way …

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 advocates to run the test suite of a project frequently, eg, for every
code change committed to a shared repository. This process imposes a high computational …