test-coverage-analyzer

You can prioritize missing tests by scoring uncovered files using domain criticality, complexity, and dependency impact. This approach helps focus on writing the most valuable tests to reduce regression and security risk before releases or after major refactors.

Yes, the analyzer automatically detects whether your project uses Jest, Vitest, or other common harnesses via configuration files. It then parses existing coverage reports or infers gaps by correlating source files with test files.

The best way to generate unit tests for critical logic is to use an analyzer that scores uncovered areas by risk and optionally scaffolds targeted test files following project-specific naming and structure patterns.

To map test coverage across domains like API endpoints and validators, run the analyzer in analyze mode. It produces a global and per-domain coverage map to pinpoint uneven coverage and highlight critical files needing tests.

You should prioritize test gaps during ongoing development before releases, after major refactors, or whenever coverage is suspected to be uneven across domains like auth, core business logic, API endpoints, validators, UI, and utilities.