test-discipline

To keep test assertions in sync with API changes, you must update relevant tests and adjust counting assertions to reflect the current repository state within the same commit. This ensures on-disk reality matches test expectations and prevents stale tests.

Stale tests block CI because they fail when API changes are not accompanied by corresponding test updates. Validating disk reality and updating test assertions before merge reduces flaky failures and keeps CI pipelines clear for other contributors.

Disk reality in test assertions refers to ensuring expected features and scenarios match the actual on-disk state. When APIs change, validating disk reality ensures that counting assertions and expected arrays accurately reflect the current repository files.

To update counting assertions for large test suites, adjust any file count or expected array references to reflect the current repository state whenever you modify public interfaces. This proactive CI hygiene practice reduces flaky failures before merge.

Yes, this approach is designed for codebases with public interfaces, large test suites, and CI pipelines where API changes frequently require corresponding test updates. It ensures on-disk state matches test expectations to reduce CI failures.