crap-score

You can calculate CRAP scores for a .NET codebase by combining cyclomatic complexity data with Cobertura XML test coverage data. This analysis identifies complex, undertested methods to help prioritize testing and refactoring efforts where they matter most.

A CRAP score quantifies code risk by combining cyclomatic complexity with test coverage data. It identifies high-risk areas that are both highly complex and undertested, enabling teams to focus their test improvements and refactoring strategies effectively.

Yes, you can compute CRAP scores at the method, class, or file scope. The analysis parses source code to determine complexity and outputs a sorted report of top offenders with risk levels and actionable remediation guidance.

The tool reads Cobertura XML coverage data and combines it with cyclomatic complexity metrics parsed from your source code. It generates a sorted report highlighting high-risk, complex, and undertested methods alongside calculated coverage targets to guide your test strategy.

Yes, the tool provides actionable recommendations for test improvements or refactoring. It outputs a sorted report of methods by CRAP score, includes risk levels, and calculates the coverage target needed to bring high-CRAP methods under your desired threshold.

The best way to guide test strategy is to compute CRAP scores using cyclomatic complexity and test coverage data. This surfaces high-risk areas in your .NET projects and provides coverage target calculations to bring complex, undertested code under control.