test-discipline

To keep tests in sync with API changes, update test assertions and expected counts in the same commit as the public interface evolution. This lockstep approach prevents test divergence and ensures CI remains green for other contributors.

Stale test assertions block CI because they no longer reflect disk reality or updated data structures. When APIs change without corresponding test updates, assertions diverge from the codebase, causing failures that block other contributors.

The best way to align test assertions with disk reality is validating that expected arrays and file counts match actual repository state. This ensures tests conform to in-repo expectations during API modifications.

Update test assertions by modifying expected values and counts in the same commit as the public API change. Ensure assertions reference actual files and data structures to maintain alignment with the current codebase state.

Preventing test divergence requires updating tests in lockstep with API changes through structured guidance. By validating that assertions reflect actual files and data structures, the process reduces reliance on manual review to catch drift.

You need to update test counts and assertions whenever public interfaces evolve, requiring test assertions to stay in sync with the codebase. This applies specifically when changes impact file counts or expected data arrays on disk.