This ‘mock’ framework consists of a number of toolkits and API that include code coverage, making this framework a little more than simple mock (or stub) objects. This framework can be used with both Junit and TestNG.

Another java code coverage tool, but this one examines performance issues when executing this type of analysis. The idea is to remove the instrumented code that has already been covered, so that it is not re-reported in subsequent runs.

Another in the genre of Junit frameworks that adds code coverage and mock objects. Anyone using Junit has a wide selection of frameworks to choose from and djUnit might fit your needs. We have not used this tool, at software testing directory, but the screen shots and features look comprehensive and truly value add, for Junit.

Another Java code coverage tool for your consideration. Supported coverage types: class, method, line, basic block. Someone may have the time to evaluate all the open source code coverage tools out there, sadly we do not have the time. However, this offering looks to be a professional solution and worth investigation by anyone considering code coverage as part of their overall testing strategy.

What makes Hansel different from other code coverage tools? Most tools try to generate code coverage reports from a test-run of all available tests. Hansel answers the question “How much of the code which a test is supposed to test is covered. Hansel gives you this information?”

Works within the Eclipse IDE to provide code coverage measures for Junit test cases. Coverage includes instructions, blocks, lines, methods and types.

"Cobertura" the Spanish and Portuguese word for "coverage.” This coverage tool shows line coverage and branch coverage so that the effectiveness of tests can be determined. Although we have not used this coverage tool we like the idea that the Java byte code is instrumented after compile, which should allow for both ease of use and no interference with the sources code.