domains / families / software-engineering / audit-tests

audit-tests

separate

Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.

When to use

• pruning redundant tests
• investigating implementation coupling
• investigating test-only production hooks
• reviewing the value of proposed coverage
• auditing an entire subsystem

When not to use

• implementing test changes
• writing and falsifying a test
• closing out resulting changes

Skill page

Source