Update failing test suites after intentional contract changes by correcting assertions, fixtures, and golden files.
npx skills add https://github.com/dhnt/dhnt --skill update-test
Please help me install this Agent Skill. Skill: update-test Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/test/update-test Command: npx skills add https://github.com/dhnt/dhnt --skill update-test
Update-test helps teams repair test suites that fail after an intentional change to the code’s public contract, ensuring tests continue to validate the new expected behavior rather than being blindly loosened or removed.
Tell the AI to update the repository’s failing tests to match the newly intended contract change by identifying every affected assertion, updating or deleting tests as appropriate, adding new coverage for the newly introduced edge cases, and then running the full test suite plus the linter.
High-intent search queries and answers about installing and using this skill.
To update failing unit tests after an intentional API contract change, you must systematically correct affected assertions, fixtures, and golden files. This ensures the test suite validates the newly expected behavior instead of being blindly loosened or deleted.
Golden files should be updated during test suite maintenance when a deliberate refactor or API modification intentionally changes return shapes. You must confirm the intended contract first, then locate and correct impacted golden files to match the new output expectations.
The best way to handle stale tests caused by renamed return fields or changed error types is to evaluate each impacted test. You can update assertions to preserve meaningful coverage, consolidate overlapping tests, or cleanly delete obsolete ones.
To add regression coverage for new edge cases introduced by a contract change, identify any new validation or error behavior resulting from the modification. Then, implement at least one new test specifically targeting those newly introduced behaviors.
Yes, updating tests for contract changes requires running the full test suite and linter. Executing the complete suite and linter verifies that all affected assertions, fixtures, and golden files align with the intended contract without introducing syntax errors.
Automated test maintenance during a refactor can prevent loosening meaningful assertions by requiring confirmation of the intended contract. It systematically locates impacted tests and preserves valuable assertions while correcting affected fixtures and golden files.
rsicarelliQuery Kotlin compiler source code to detect breaking API changes.
Marshall-HallenbeckGenerate unit tests for Python, JavaScript, TypeScript, Rust, and Go modules.
opsMachineGenerate failing unit and integration tests from approved Test Plan criteria.
ksmuvvaGenerate unit, integration, and end-to-end test suites with fixtures and coverage analysis.
