ln-634-test-coverage-auditor

The audit scans production code for money-related, security-related, data-related, and core-journey paths, then classifies missing tests by domain and severity. This generates a prioritized markdown report to guide test improvements.

Domain-aware test coverage gap analysis tags missing tests by specific business domains like Money, Security, and Data Integrity. It scopes and classifies test gaps based on the functional area of the production path to prioritize remediation.

You generate a quality gate report by running the audit against your codebase. It produces a consolidated markdown file named 634-coverage-gaps.md that details missing tests for critical business paths and prioritizes test improvements.

Yes, the coverage auditor specifically scans for security-related and data-related paths in production code. It identifies missing tests for these critical areas and includes them in the consolidated markdown report.

The best way to prioritize missing tests is to run an audit that classifies coverage gaps by domain and severity. It tags findings for core journey paths to guide your test improvements effectively.

No external dependencies or components are required. The test coverage audit relies on a domain-aware scan path and test metadata to analyze production paths and generate the coverage gaps report.