https://gibbok.github.io/myvar/tags/code-quality-software-metrics-refactoring/Recent content in Code-Quality-Software-Metrics-Refactoring on MyVar.devHugoen-USSun, 30 Aug 2026 07:29:36 +0000https://gibbok.github.io/myvar/code-quality-metrics/cyclomatic-complexity-and-crap-metrics-guide/Sun, 30 Aug 2026 07:29:36 +0000https://gibbok.github.io/myvar/code-quality-metrics/cyclomatic-complexity-and-crap-metrics-guide/<h2 id="overview">Overview</h2> <p>Cyclomatic Complexity and Change Risk Anti-Patterns (CRAP) are essential software engineering metrics used to evaluate code maintainability, testability, and modification risk. Cyclomatic Complexity measures execution paths within a function, while CRAP combines complexity with code coverage to quantify the risk of introducing defects during changes.</p> <h2 id="key-insights">Key Insights</h2> <ul> <li><strong>Execution Path Tracking:</strong> <strong>Cyclomatic Complexity</strong> quantifies the number of independent execution paths in code, directly impacting test effort and readability.</li> <li><strong>Exponential Risk Penalty:</strong> The <strong>CRAP score</strong> heavily penalizes complex logic that lacks automated tests, highlighting high-risk areas in pull requests and code reviews.</li> <li><strong>Dual-Path Remediation:</strong> High CRAP scores can be lowered either by <strong>reducing code complexity</strong> through refactoring or by <strong>increasing test coverage</strong>.</li> <li><strong>Target Thresholds:</strong> Maintain a Cyclomatic Complexity score below <strong>10</strong> and a CRAP score under <strong>30</strong> to ensure code stability.</li> </ul> <h2 id="technical-details">Technical Details</h2> <h3 id="cyclomatic-complexity">Cyclomatic Complexity</h3> <p>Cyclomatic Complexity calculates structural complexity based on control flow branches. Every function starts with a baseline score of 1 and increases by 1 for each conditional branch or iteration construct.</p>