crap-score

To calculate CRAP score, combine cyclomatic complexity from decision constructs with per-method line hit rates extracted from Cobertura XML coverage, then compute sorted values to pinpoint risky code.

A CRAP score identifies change risk anti-patterns by measuring code that is both highly complex and inadequately tested, targeting refactoring and test investment toward specific risky methods.

Yes, you need Cobertura XML coverage output. If missing, you must run dotnet test with coverage collection to extract real execution data and calculate accurate CRAP scores.

Yes, you can compute CRAP scores for a named .NET method, class, or single source file by counting decision constructs for complexity and extracting method-level line hit rates.

The best way to prioritize test writing is computing sorted CRAP values and following threshold-based recommendations, which specify the exact coverage needed or when complexity reduction is required.

You should reduce cyclomatic complexity instead of adding tests when threshold-based recommendations indicate that complexity reduction is required to lower the CRAP score effectively.