testing-anti-patterns

From README

Testing Anti-Patterns You are identifying and avoiding common testing anti-patterns. Review Workflow Follow these steps when reviewing test code: Run tests in isolation — Verify each test passes independently (no shared state, no ordering dependency). Check for patterns below — Scan for each anti-pattern in the checklist; flag every match with the specific defect. Apply refactoring strategy — Use the refactoring strategies section to select and apply the appropriate fix. Verify the test still fails when code breaks — After fixing, confirm the corrected test catches real regressions (remove or stub the implementation to confirm a failure occurs). Critical Anti-Patterns The Liar - Tests That Always Pass Problem: Test passes even when the code is broken. Detection: Remove or break the implementation - test should fail. The Giant - Tests Too Large Problem: Single test covers too many behaviors. Fix: One test, one logical assertion concept.