test-standards

Test quality scanning identifies anti-patterns like missing assertions, tautological checks, and error-swallowing in your JavaScript and TypeScript tests. Run the scanner on your test directory to produce structured findings that reveal which tests validate behavior meaningfully versus passing trivially, enabling targeted fixes before code ships.

Mesa-optimization occurs when tests pass without validating core behavior; vacuous assertions check conditions that are always true. These anti-patterns make tests unreliable at catching regressions. The scanner detects both patterns across JavaScript, TypeScript, and Python test files so you can strengthen coverage and ensure assertions genuinely validate behavior.

Yes, the scanner validates test quality across JavaScript, TypeScript, and Python test suites simultaneously. It flags the same anti-patterns—no assertions, tautological checks, mock-only validation, and error-swallowing—in all three languages, producing unified JSON output suitable for CI integration regardless of your test stack.

The scanner outputs deterministic, structured JSON reports designed for CI integration. Run `python scripts/test_quality_scanner.py ./tests --format json` or specify an output file with `--output test-quality-report.json` to generate findings that automation workflows can parse, route to developers, and use for gating test changes during validation.

Error-swallowing patterns and missing async protections allow bugs to hide in production. The scanner flags these issues to help you identify tests that silently ignore failures, enabling you to add proper exception handling and async validation so tests reliably catch real defects before deployment.

Yes, the scanner is designed to validate test quality after test changes occur, including modifications by automation agents. It applies pattern-based detection during QA validation, test creation, and maintenance workflows to ensure meaningful coverage and robust behavior remain intact across all test changes.