test-discipline

Test assertions break because they reference stale disk state like file counts or arrays. When APIs change without updating tests in the same commit, test suites drift and block CI pipelines.

To keep tests in sync with API changes, update test assertions and documentation in the same commit as the API modification. This aligns test expectations with actual disk reality and prevents drift.

Test-suite drift occurs when tests reference outdated disk state such as file counts or arrays. Stale tests no longer match actual files, causing CI failures and degrading test integrity over time.

Yes, this approach specifically applies to codebases where tests reference disk state like counts and arrays. It enforces updating those tests in the same commit to match actual files across CI pipelines.

The best way to prevent stale tests from blocking CI is enforcing test discipline by updating tests, assertions, and documentation in the same commit whenever APIs or public interfaces change.

You should update test assertions whenever APIs or public interfaces change. Updating tests in the same commit maintains CI reliability by aligning test updates with code modifications.