GMetrics 0.5 = Groovy + CRAP
The GMetrics project provides calculation and reporting of size and complexity metrics for Groovy source code. Version 0.5 adds 3 new metrics, as well as bug fixes and enhancements. You can now calculate the popular and useful CRAP metric for your Groovy code.
- New CrapMetric. Calculates the CRAP score for a method, based on its complexity and code coverage. Requires a Cobertura "coverage.xml" file (and CoberturaLineCoverageMetric). See this blog post describing the CRAP metric. (#3192158)
- New CoberturaBranchCoverageMetric. Branch coverage at method/class/package level. Requires a Cobertura "coverage.xml" file. (#3474462)
- New CoberturaLineCoverageMetric. Line coverage at method/class/package level. Requires a Cobertura "coverage.xml" file. (#3474462)
Bug Fixes and Enhancements
- Method-level Metrics: Handle multiple overloaded methods. (#3439103).
- Fix: For SingleSeries package-level reports, show the full package name, not just the rightmost part of the package name. (#3439104).
- Add includeClosureFields property to AbstractMethodMetric. Defaults to true.
Integration with CodeNarc
- If you use GMetrics with CodeNarc, this release requires CodeNarc 0.16.
See the README file for more details.Visit the GMetrics Home Page
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)