pytest-coverage

Pytest coverage identifies untested lines by running pytest with coverage to produce per-file reports and an annotated view of missing lines. You can inspect coverage per module to locate gaps and iteratively add tests to reach comprehensive coverage.

Cov_annotate generates an annotated view of missing lines in your Python modules. It produces artifacts that guide test expansion by highlighting specific untested code blocks across the project, helping you prioritize test improvements during refactors.

Yes, pytest-cov integration is required to run the coverage workflow and generate the per-file reports. You also need cov_annotate-generated artifacts present in your project to guide targeted test expansion and achieve near-100% coverage.

To boost pytest coverage to 100 percent, run the coverage workflow to identify untested lines, inspect the annotated outputs to locate missing code blocks, and iteratively add tests targeting those specific gaps across your Python modules.

Yes, you can use cov_annotate outputs to prioritize test improvements during refactors or feature additions. The annotated view shows exactly which lines lack coverage, allowing you to target untested code blocks efficiently.

The approach requires cov_annotate-generated artifacts to be present and depends on pytest-cov integration. It targets untested code blocks based on line coverage data, so achieving near-100% coverage requires iterative manual test additions guided by the reports.