exp-test-smell-detection

# Test Smell Detection Deep formal audit of test code using an academic test smell taxonomy. Detects symptoms of bad design or implementation decisions that make tests harder to understand, more fragile, less effective at catching bugs, or more expensive to maintain. Produces a severity-ranked report with specific locations and actionable fixes. ## Why Test Smells Matter Test smells erode confidence in a test suite and inflate maintenance costs: | Problem | Consequence | |---------|-------------| | Tests with conditional logic | Some paths never execute — hidden testing gaps | | Tests that depend on external resources | Flaky failures, slow execution, environment coupling | | Tests that sleep to wait for results | Non-deterministic timing, slow suites, false failures | | Tests without assertions | False confidence — coverage looks good but nothing is verified | | Tests that call many production methods | Hard to diagnose failures, unclear what's being tested | | Tests with magic numbers | Unreadable intent, unclear boundary conditions | | Tests relying on ToString for comparison | Brittle to formatting changes, obscure failure messages | | Tests with exception handling logic | Swallowed failures, tests that pass when they shouldn't | ## When to Use - User asks for a comprehensive or formal test smell audit - User asks "are my tests well-written?" and wants a thorough analysis - User wants a test quality health check with academic rigor - User asks for a review of test d...