Can I use this in my CI/CD pipeline?

Yes, the skill includes standardized configurations for integrating coverage reports into CI tools like GitHub Actions and services like Codecov.

Does it automatically write tests for me?

While it identifies untested code, this skill focuses on reporting and analysis. You can pair it with the 'phase-test-tdd' skill to help generate the actual test cases.

What is the difference between line and branch coverage?

Line coverage measures which lines of code were executed, while branch coverage ensures every decision point (like if/else statements) was tested in every possible direction.

What programming languages does this skill support?

This skill provides specific implementation patterns for Mojo and Python using Pytest, though the workflow concepts apply to most modern development environments.

Test Coverage Reporter

Name: Test Coverage Reporter
Author: mvillmow

bymvillmow

•

Security & Testing

Generates and analyzes detailed test coverage reports to identify untested code paths and ensure high software quality.

About

The Test Coverage Report skill empowers developers to maintain robust codebases by providing automated insights into test execution across Python and Mojo projects. It streamlines the process of generating line and branch coverage metrics, helping teams identify specific gaps in their testing suites before pull requests are submitted. By facilitating both terminal-based summaries and rich HTML reports, this skill ensures that critical logic paths are thoroughly verified and that projects consistently meet their defined coverage thresholds and quality benchmarks.

Key Features

Precise identification of untested code lines and missing logic branches
Automated generation of line and branch coverage metrics
Detailed terminal and HTML report output for visual code analysis
Seamless integration patterns for CI/CD workflows and automated quality checks
12 GitHub stars
Support for defining and verifying minimum and target coverage goals

Use Cases

Identifying blind spots in complex Mojo or Python logic for improved reliability
Automating quality reporting within continuous integration pipelines
Validating test coverage before merging pull requests to prevent regressions

About

Key Features

Precise identification of untested code lines and missing logic branches
Automated generation of line and branch coverage metrics
Detailed terminal and HTML report output for visual code analysis
Seamless integration patterns for CI/CD workflows and automated quality checks
12 GitHub stars
Support for defining and verifying minimum and target coverage goals

Use Cases

Identifying blind spots in complex Mojo or Python logic for improved reliability
Automating quality reporting within continuous integration pipelines
Validating test coverage before merging pull requests to prevent regressions