test-discipline

To keep test assertions in sync when APIs change, you should update tests in the same commit as the API modification. This prevents stale assertions and avoids CI failures by ensuring disk reality matches expected values.

CI pipelines fail after updating public interfaces because test assertions become stale if they are not updated in the same commit. Synchronizing tests with the evolving API contract ensures disk reality matches expected values across releases.

CI guardrails for detecting stale test assertions are mechanisms that identify when expected file counts, lists, or arrays no longer match disk reality. They guide developers to maintain consistency by updating tests alongside code changes.

To update expected file counts and arrays in test suites, you must sync test assertions with disk reality by modifying the expected values in the same commit that changes the repository state or API contract.

You need to update tests for API changes whenever a public interface evolves to avoid CI failures. Keeping tests aligned with the updated codebase requires modifying file counts, lists, and API contracts in the same commit.

Syncing tests with disk reality works for file count assertions by detecting when expected values no longer match the repository state. This applies to test suites relying on file counts, arrays, and API contracts across CI environments.