Metrics Must be Interpreted In Context
James Newkirk points out that the absolute measurement of code coverage is not a very interesting number by itself, but must be viewed as part of the overall trend of coverage. He also points out that...
View ArticlePanopticode 0.1 Is Released
Panopticode 0.1 is now available. While there are still some rough edges, this release provides: Treemaps of code coverage Treemaps of complexity Integrates metrics from Emma, JavaNCSS, and JDepend...
View ArticleNew Tool: Complexian
Marty Andrews has just released version 0.12.0 of Complexian. This version adds the ability to output to plain or XML files. Complexian is a tool for very quickly measuring NPATH and CCN of Java...
View ArticleTeaser: Creating Ad Hoc Reports in Panopticode 0.2
In Metrics Must be Interpreted In Context I described one of my preferences when creating rules around metrics. Namely, that one should not look at metrics independently, but within the context of...
View ArticleTeaser: Breaking the Build in Panopticode 0.2
In the last post we learned that Panopticode 0.2 will allow us to create arbitrary reports using a SPARQL SELECT query. Another feature in Panopticode 0.2 is to use a SPARQL ASK query to break the...
View ArticleNew Metric: C.R.A.P.
The good folks at Agitar have proposed a new metric, C.R.A.P and an Eclipse plugin crap4j for executing it. C.R.A.P. combines a method’s complexity with its coverage to come up with a single number...
View Article
