guarding-test-quality

Fake test detection identifies tests that don't validate actual behavior—tautologies, empty tests, and over-mocked patterns. This Skill automatically analyzes test authenticity during /ultra-test runs and test file edits, calculating a Test Authenticity Score (TAS) to measure meaningful coverage beyond line percentages, blocking task completion if quality falls below 70%.

Test Authenticity Score (TAS) measures test meaningfulness using weighted components: mock ratio (25%), assertion quality (35%), real execution (25%), and anti-pattern detection (15%). A minimum TAS of 70% is required to pass quality gates; scores below this threshold block task completion.

Test quality analysis triggers during /ultra-test runs, when test files (*.test.ts, *.spec.ts, *.test.js, *.spec.js) are edited, when tasks are marked complete with tests, and on keyword-driven triggers like 'test quality', 'TAS score', 'mock ratio', 'fake tests', or 'assertion count'.

Anti-pattern detection identifies tautology tests (assertions that always pass), empty tests (no real assertions), and over-mocking patterns that simulate behavior without testing actual code execution. Critical anti-patterns block task completion regardless of overall TAS score.

Yes. This Skill integrates directly with your test files during /ultra-test runs and test file edits across TypeScript and JavaScript projects (.test.ts, .spec.ts, .test.js, .spec.js files), requiring no additional setup or dependencies.