domains / families / software-engineering / test-smell-detection

test-smell-detection

separate

Audits existing tests in any language using formal, research-backed test smell names and the testsmells.org 19-smell academic taxonomy. Use when the caller asks for an academic or citable test-smell review, named smell categories, or a formal severity-ranked smell assessment. Covers Assertion Roulette, Conditional Test Logic, Mystery Guest, Eager Test, Sleepy Test, Unknown Test, Sensitive Equality, and the rest of the catalog across .NET, Python, JavaScript/TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. DO NOT USE FOR a quick pragmatic test review (use test-anti-patterns), writing or running tests, framework migration, coverage, or assertion-diversity metrics.

When to use

• Audit only staged or named tests. Search the current workspace before asking
• Read production code only when it changes a verdict.
• For unfamiliar framework APIs, read the matching language file relative to
• Read [the complete catalog](references/test-smell-catalog.md) when the caller

When not to use

• quick pragmatic test review
• writing or running tests
• framework migration
• coverage
• assertion-diversity metrics

Skill page

Source