test-helper

Implementation-first discovery traces source code call chains and I/O to ensure tests reflect current behavior rather than stale assumptions. It maps actual implementation logic to verify the module's contract before rewriting any test code.

Contract-based rewriting generates a clear checklist of observable behaviors before modifying any test code. It ensures new test cases accurately verify the module's contract by mapping current implementation logic instead of patching brittle assertions.

Yes, this approach applies to both unit and integration testing workflows where test suites have become decoupled from production logic. It systematically discovers call chains and verifies test coverage against implementation branches.

Invoke the test-helper skill to analyze the current directory and systematically rewrite test cases to match the implementation. It traces call chains, defines contracts, and verifies test coverage against implementation branches automatically.

Test suites drift from actual implementation over time, leading to false positives, outdated assertions, or brittle tests that fail due to minor refactors. Aligning test cases with current system behavior resolves this decoupling issue.

Rewriting test cases to match implementation logic risks validating incorrect behavior if the production code itself is flawed. Contract-based rewriting mitigates this by defining observable behaviors first, ensuring tests verify the intended contract.