Testing Reliability

Make tests detect the behavior they claim to cover and make failures attributable. Use this skill to repair the test signal; test-driven-development owns the test-first implementation loop.

When to activate

• Flaky, timing-sensitive, or order-dependent tests.
• Heavy mocks, unclear patch targets, or fakes that do not match real behavior.
• Production code changed only to make tests easier.
• Coverage increased without stronger assertions.
• Surviving or uncovered mutants in behavior that matters.
• CI failures that cannot be reproduced locally.

Reliability workflow