test-coverage-report

To identify test coverage gaps from coverage.xml or lcov.info, scan the report to find modules falling below a defined threshold. This flags specific file paths and line references to guide remediation without executing any tests.

Yes, you can check module coverage thresholds without running tests by analyzing a pre-generated coverage report. This approach reads existing outputs like coverage.xml to evaluate gaps against a threshold defined in AGENTS.md.

Test coverage gap prioritization works by ranking modules based on how far they fall below a defined threshold. This highlights critical areas and outputs a prioritized list with exact file paths to guide remediation.

To generate a prioritized testing gaps report, you need a project with a recent pre-generated coverage output such as coverage.xml or lcov.info, and a defined coverage threshold in AGENTS.md. The analysis reads these inputs to produce ranked gaps.

You should avoid analyzing a pre-generated coverage report when the coverage output is outdated or when you need to execute tests to gather fresh metrics. This approach relies entirely on existing coverage data to flag gaps.