[Forgot to Reply All, again. Sorry.] Hey Christoph,
There's a few things that have happened in the last couple months with JBlanket. Let me sum it up and see if it jives with what you'd like. Excluding constructors requires setting a separate option in the Ant task. Is that being done for the Hackystat builds? 0 line void methods (as well as abstract ones) are marked as untestable in JBlanket 4.4, but Hackystat doesn't yet recognize that category (it's a new JBlanket feature and there's been lots of other stuff for Hackystat). Only methods that are exactly 1-line are excluded by JBlanket in the "exclude one line methods" option. Hope that helps. --Tim On 4/15/05, Christoph <[EMAIL PROTECTED]> wrote: > Hi. > > I just looked through the JBlanket result pages and found something strange: > I have a lot of utility classes (classes with only static methods) which > have a private, empty constructor (so that nobody can create an > instance). Strange thing is, JBlanket is complaining that this empty > constructor is not covered with tests (of course not - there is no way > of invoking that thing). Shouldn't JBlanket exclude 0-line methods or > constructors? (It excludes 1-liner...) > Right now, it is impossible for me to archive 100% coverage for utility > classes. > Is that bug or feature? (I vote for bug). > > Cheers, > Christoph >
