test-discipline

To prevent CI failures from out-of-date tests, you must update tests in the same commit as API changes. This ensures test synchronization and validates test assertions against actual disk state, maintaining overall test integrity.

Validating test assertions against disk reality involves checking that assertions referencing expected file counts or arrays match the actual disk state. This synchronization prevents CI failures caused by tests referencing outdated file structures.

Test synchronization is the process of updating tests simultaneously with API changes to maintain test coverage. You need it whenever modifying public interfaces to ensure test assertions remain in sync with the actual disk reality and prevent CI failures.

The best way to maintain test integrity during CI flow enhancements is to require test updates within the same commit as API changes. This approach validates test assertions against disk reality and reduces CI failures caused by desynchronized codebases.

CI pipelines fail when test assertions reference incorrect file counts because the tests are out of sync with the actual disk reality. Updating test assertions in the same commit as API changes resolves this test integrity issue and prevents failures.

Yes, the test-discipline skill works without external dependencies to ensure test synchronization. It uses internal scripts to validate that test assertions match disk reality and that tests are updated in the same commit as API changes.