Can I use this in my CI/CD pipeline?

Yes, this skill provides pre-configured templates for GitHub Actions and Azure Pipelines to automate coverage collection, report generation, and artifact uploading.

What is a CRAP score?

The CRAP (Change Risk Anti-Patterns) score is a metric that combines cyclomatic complexity with code coverage to determine how risky a piece of code is to maintain or change. High scores indicate complex, untested code.

What tools need to be installed for this skill to work?

You need the .NET SDK, the 'XPlat Code Coverage' collector (standard with most test templates), and the ReportGenerator tool installed either globally or as a local dotnet tool.

How do I interpret high CRAP scores?

A CRAP score over 30 is considered high risk. You should either add more unit tests to increase coverage or refactor the method to reduce its cyclomatic complexity.

Why does this skill require the OpenCover format?

The OpenCover format is necessary because it includes the cyclomatic complexity metrics required for CRAP score calculation, which many other coverage formats omit.

.NET CRAP & Coverage Analysis

Name: .NET CRAP & Coverage Analysis
Author: Aaronontheweb

byAaronontheweb

•

203

Seguridad y Pruebas

Analyzes code coverage and complexity metrics to identify high-risk code using the CRAP (Change Risk Anti-Patterns) score.

Acerca de

This skill empowers .NET developers to quantify technical debt and code risk by integrating code coverage data with cyclomatic complexity. By calculating CRAP scores via OpenCover and ReportGenerator, it identifies 'risk hotspots'—complex code paths that lack sufficient testing. It provides automated workflows for setting up coverage collection, generating interactive HTML reports, and enforcing quality thresholds in CI/CD pipelines, ensuring that critical logic is never left untested before modification or deployment.

Características Principales

203 GitHub stars
Standardized coverage.runsettings configuration optimized for .NET projects
CI/CD integration templates for GitHub Actions and Azure Pipelines
Automated CRAP score calculation using cyclomatic complexity and coverage data
Configurable coverage thresholds to enforce quality standards in pull requests
Interactive HTML report generation with visual Risk Hotspot identification

Casos de Uso

Prioritizing testing efforts by focusing on complex methods with low coverage
Establishing automated code quality gates within CI/CD workflows
Identifying high-risk legacy code that requires immediate refactoring or unit tests

Acerca de

Características Principales

203 GitHub stars
Standardized coverage.runsettings configuration optimized for .NET projects
CI/CD integration templates for GitHub Actions and Azure Pipelines
Automated CRAP score calculation using cyclomatic complexity and coverage data
Configurable coverage thresholds to enforce quality standards in pull requests
Interactive HTML report generation with visual Risk Hotspot identification

Casos de Uso

Prioritizing testing efforts by focusing on complex methods with low coverage
Establishing automated code quality gates within CI/CD workflows
Identifying high-risk legacy code that requires immediate refactoring or unit tests