test-discipline

To keep automated tests in sync when APIs change, update the affected test assertions in the same commit as the API modifications. This ensures test expectations match actual disk content and prevents CI failures caused by stale tests.

Stale tests block CI pipelines because test assertion arrays diverge from actual disk content after API changes. When files are added or removed without updating expectations, automated tests fail, blocking merges for other contributors.

Update test expectations across modules by modifying test assertion arrays in the same commit after API changes. Run the test suite to verify consistency and ensure assertions reflect actual file counts and public interfaces on disk.

You need to update test assertions to match disk reality whenever APIs or public interfaces change. Updating tests in the same commit as API changes ensures assertion arrays reflect actual disk content and fail when they diverge.

Yes, this test synchronization approach works with existing CI pipelines. It applies to projects with automated tests that reference file counts or public interfaces across modules, ensuring assertion arrays reflect actual disk content to avoid blocking CI.

Test-API drift occurs when APIs or public interfaces change but test assertions are not updated in the same commit. It causes automated tests to fail because assertion arrays no longer reflect actual disk content, blocking CI pipelines for contributors.