Baidu's Continuous Integration Practices: Test Coverage, Build System Design, and Team Habits

Baidu's continuous integration (CI) series explains how the company leverages a unified CI capability model focused on three core elements—test coverage, build system, and process standards—to quantify and improve software quality.

Test Coverage is presented as the soul of CI, with considerations for selecting appropriate test types such as code inspection, unit testing, functional testing, performance testing, stress testing, and product integration testing. Three key factors guide the selection:

1. Overall and Partial Integration : Both product‑level and component‑level tests are needed to expose issues early and ensure the whole system can be released confidently.

2. Efficiency and Stability : Tests must provide rapid feedback and produce reliable, repeatable results, avoiding flaky outcomes caused by environmental variability.

3. Fit to Product Line Context : Specific product characteristics dictate additional tests, such as compatibility testing for diverse devices or strategy‑effect evaluation for algorithms.

Build System design follows three principles:

1. Reuse : Reusing resources, test frameworks, environments, and test artifacts improves efficiency and reduces maintenance overhead.

2. Reasonable Pipeline Design : A well‑structured test pipeline links selected test coverage stages, avoids unnecessary concurrent executions, and triggers tests based on the nature of code changes (e.g., skipping system‑level tests for pure unit‑test changes).

3. Service‑Oriented Architecture : Treating the build system as a service facilitates broader adoption across multiple product lines while managing integration and maintenance costs.

Team Habits emphasize two practices to sustain the CI system:

1. Increase Team Attention : Everyone is responsible for the stability of the build system; issues must be owned and resolved promptly to maintain trust in test results.

2. Reduce Impact of Non‑Standard Commits : Developers should test locally and submit clean code to avoid large failure cascades, fostering a culture of disciplined contributions.

The article also includes diagrams illustrating the CI test coverage composition and the overall CI system interaction flow.

Future installments will cover CI best‑practice “ice‑breaking” journeys.