domains / families / software-engineering / test-gap-analysis

test-gap-analysis

separate

Find caller-visible production changes existing tests would miss through pseudo-mutation analysis; verify candidates or close gaps only when requested. Includes read-only per-test composition for grading. Polyglot. USE FOR: would tests catch a bug, behavioral blind spots, surviving mutations. DO NOT USE FOR: concrete fix/feature revision proof (test-value-evidence); suite taxonomy (test-tagging); .NET coverage, Cobertura, plateaus or coverage-backed priorities (coverage-analysis); named CRAP (crap-score); new suites (code-testing); assertion/smell audits; mutation tools.

When to use

• would tests catch a bug
• behavioral blind spots
• surviving mutations
• per-test-read-only assessment
• inventory public outcomes
• verify candidates
• close gaps
• exhaustive audit

When not to use

• concrete fix/feature revision proof
• suite taxonomy
• .NET coverage
• Cobertura
• plateaus
• coverage-backed priorities
• named CRAP
• new suites

Skill page

Source