Cenqua has released Clover 1.3.12, a $250 payware unit test coverage tool. 1.3.12 "is a bugfix release. It addresses a problem that prevented Clover-instrumented classes from loading correctly in JBoss 3.x under some conditions. It also includes various minor improvements and bugfixes." Clover modifies the source code to enable it to follow which statements are executed when, and keeps a running count of how many times each statement is executed during the test suite. Any statement that executes zero times is not being tested. I use Clover with Ant, but there are also versions for NetBeans, Eclipse, IntelliJ IDEA, and Oracle JDeveloper 10g. Clover can generate test coverage reports in XML, HTML, PDF, or via a Swing Viewer. Java 1.2 or later is required.
As usual I tested this release on XOM. I've been doing some updates on XOM lately, so I was curious to see how the code coverage was holding up. Externally the changes since the 1.1 release in November are quite minor, but internally I'd completely rewritten one class, and made very significant changes in several others since the last time I measured the coverage. A few things I noticed:
Element.attributeIteratorcan probably skip a hasNext check if I trust Jaxen- I'm missing a test for serializing elements whose namespace prefix is
xml(or perhaps I'm making an unnecessary test for that). - I need some tests for serializing three or more consecutive text nodes when using NFC.
- I seem to be missing some very important tests for serializing additional namespace declarations. That's very surprising. I'm pretty sure I have such tests. More likely some of the changes I recently made mean that's happening elsewhere in the code base now, and the apparently untested code is dead code I can eliminate.
- Likewise, there's some either dead or untested code in the
DOMConverter.convert()method. This was one of the major changes since the last release. DOMConvert.convert(Attr attribute, NodeFactory factory)is completely untested. That's very surprising. This is probably a real bug (though in new code, not old code).DOMConvert.convert(Element, NodeFactory)has an untested block that might be dead code.
They're a few other places that appear to be minor uncovered fragments, nothing too shocking. I'll have to look into these in more detail. Bottom line: if it isn't tested, it is buggy.