test-smell-detection

Test smell detection scans test methods and classes for categorized design smells like conditional logic, mystery guests, and magic numbers, producing a severity-ranked report with actionable remediation examples to improve suite reliability and maintainability.

Common fragile test patterns include sleepy tests, sensitive equality, over-broad fixtures, and mystery guests. These hidden dependencies and timing issues make suites misleading and expensive to maintain, requiring a taxonomy-driven health check to identify and resolve.

Yes, you can run a test smell audit on a full test project. The audit applies to unit, integration, and broader test-project scenarios, performing a taxonomy-driven health check of test structure and behavior across the provided files.

High maintainability costs often stem from assertion-free tests, eager tests, and ignored or disabled tests. A formal smell audit identifies these categorized design patterns, calibrates severity for contextual cases, and provides concrete fix guidance.

The best way to audit test code quality for hidden dependencies is using a research-taxonomy smell audit aligned with the testsmells.org taxonomy. This approach systematically detects mystery guests and over-broad fixtures, producing findings that are easier to prioritize and discuss.

Yes, test smell detection works for integration testing contexts. The audit calibrates severity specifically for common integration test scenarios, ensuring the reported locations and actionable remediation guidance are appropriate for the specific test structure and behavior being analyzed.