Enforce test updates in the same commit as API changes.
npx skills add https://github.com/robpitcher/eShopOnWeb --skill test-discipline-robpitcher
Please help me install this Agent Skill. Skill: test-discipline Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/test-discipline Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill test-discipline-robpitcher
When APIs or public interfaces change, tests must be updated in the same commit. Stale tests block CI for other contributors.
Update the related tests in the same commit whenever you modify an API.
High-intent search queries and answers about installing and using this skill.
Stale tests block CI for other contributors when APIs or public interfaces change, so updating test assertions and fixtures in the same commit prevents pipeline failures and maintains consistency across the codebase.
You update test assertion arrays and API surface checks to match the new disk state counts or public interface modifications, including these updated test fixtures in the exact same commit as the API change.
Yes, this approach applies directly to codebases where tests rely on disk state counts or public interfaces, enforcing that test fixtures and assertions are updated in the same commit as API surface changes.
Stale tests block CI for other contributors because outdated assertions fail against modified public interfaces, halting the continuous integration pipeline until the test fixtures are updated to match the API changes.
The best way to enforce in-commit test updates is to apply automated checks that verify test fixtures and assertion arrays are modified in the same commit as the public interface or API change.
ronniegeraghtyUpdate test assertions in the same commit as API changes.
Izak90Update tests in the same commit after API changes to prevent CI failures.
mpauloskyEnforce same-commit test updates for API and counted-resource changes.
quaid-appUpdate test assertions and build checks when public interfaces change.
