test-coverage

A test pyramid health check audits the balance of unit, integration, and e2e layers to spot missing coverage and anemic setups. It reviews your Vitest and Playwright layers to identify critical flows lacking tests and ranks them by severity using concrete file evidence.

False confidence in test coverage stems from defects in existing tests like shape-only assertions, tautological mocks, skipped tests, and happy-path-only coverage. An audit identifies these misleading tests by flagging brittle selectors and isolated successes that fail to validate actual logic branches.

To check for gaps versus defects, run a read-only test audit that classifies findings into missing coverage (gaps) and misleading validations (defects). This process evaluates your test pyramid to determine whether critical flows are untested or if existing tests contain tautological mocks and brittle selectors.

A test coverage audit does not modify test code. It performs a read-only review of your codebase test pyramid to output evidence-based, ranked findings with severity, gap-vs-defect classification, and concrete suggested fixes without altering your current test implementations.

You need a test coverage review when you suspect an anemic test pyramid or false confidence in your test suite. It applies to requests for test audits and health checks, specifically evaluating unit (Vitest) and e2e (Playwright) layers to identify missing branches and dangerous test defects.

The best way to find brittle selectors and skipped tests is through a defect detection audit of existing tests. This process flags misleading tests such as skipped or .only tests, tautological mocks, and brittle selectors within your Playwright e2e suite to eliminate false confidence.