domains / families / software-engineering / test-value-evidence

test-value-evidence

separate

Assess tests for an identified code or test change, feature, PR or commit. USE FOR: review changed behavior or regression tests, prove pre-fix/missing behavior is detected, revision-bound red-green evidence. Polyglot. DO NOT USE without an identified change: hypothetical mutations or general suite blind spots (test-gap-analysis). Also exclude per-test readiness/A-F grades (grade-tests), coverage (coverage-analysis), new suites (code-testing), or mutation engines.

When to use

• review changed behavior or regression tests
• prove pre-fix/missing behavior is detected
• revision-bound red-green evidence
• assess changed contracts and directly related tests

When not to use

• hypothetical mutations
• general suite blind spots
• per-test readiness/A-F grades
• coverage analysis
• new suites
• mutation engines
• tasks without an identified change

Skill page

Source