OSS Code Coverage

[resplin]

Obsolete Pages{{Obsolete}}

The official documentation is at: http://docs.alfresco.com

OSS QA Tools
Back to OSTT

---

Table of Contents

• 1 EMMA


• 2 Clover


• 3 Quilt


• 4 NoUnit


• 5 InsECT


• 6 Hansel


• 7 Jester


• 8 JVMDI Code Coverage Analyser


• 9 GroboCodeCoverage


• 10 jcoverage/gpl


• 11 JBlanket

EMMA

EMMA is an open-source toolkit for measuring and reporting Java code coverage. EMMA distinguishes itself from other tools by going after a unique feature combination: support for large-scale enterprise software development while keeping individual developer's work fast and iterative at the same time. Every developer on your team can now get code coverage for free and they can get it fast! EMMA is so lightweight developers can use it during the process of writing tests instead of waiting for a 'test build'. This gets code coverage where it belongs: helping with design and implementation before the code is checked in.

http://emma.sourceforge.net/

Clover

NOTE: This is not free!

Clover provides method, branch and statement coverage for projects, packages, files and classes. Unlike tools that use bytecode instrumentation or the JVM Profiling API, Clover accurately measures per statement coverage, rather than per-line coverage.

http://www.cenqua.com/clover/

Quilt

Quilt is a Java software development tool that measures coverage , the extent to which unit testing exercises the software under test. It is optimized for use with the JUnit unit test package, the Ant Java build facility, and the Maven project management toolkit.

http://quilt.sourceforge.net/

NoUnit

NoUnit allows you to see how good your JUnit tests are. It generates a report from your code to graphically show you how many of your project's methods are being tested , and how well.

http://nounit.sourceforge.net/

InsECT

InsECT which stands for Instrumentation Execution Coverage Tool, is a system developed in Java to obtain coverage information for Java programs. InsECT instruments (inserts instructions into) Java class files at the bytecode level with probes to report information about a system at runtime. The goal of InsECT is to provide detailed coverage information about Java programs by taking into full account the object-oriented behavior and language features of Java. Furthermore, as an open-source project, InsECT is designed to be extensible for use in a wide variety of dynamic analyses. InsECT utilizes the Byte Code Engineering Library.

http://insectj.sourceforge.net/

Hansel

Hansel is an extension to JUnit that adds code coverage testing to the testing framework.

http://hansel.sourceforge.net/

Jester

Jester finds code that is not covered by tests. Jester makes some change to your code, runs your tests, and if the tests pass Jester displays a message saying what it changed. Jester includes a script for generating web pages that show the changes made that did not cause the tests to fail.

http://jester.sourceforge.net/

JVMDI Code Coverage Analyser

This small utility is a shared library which when loaded into a Java VM (1.4+) which supports JVMDI will record all the lines of code executed. This is a relatively coarse coverage method, but good enough for a lot of purposes.

http://jvmdicover.sourceforge.net/

GroboCodeCoverage

GroboCodeCoverage is a 100% Pure Java implementation of a Code Coverage tool. It uses Jakarta's BCEL platform to post-compile class files to add logging statements for tracking coverage.

http://groboutils.sourceforge.net/codecoverage/index.html

jcoverage/gpl

jcoverage/gpl is a free code-coverage tool for Java™ programmers that allows them to measure the effectiveness of their Java tests and how much of a software program's code has been tested. jcoverage/gpl identifies how many times each line of code in your application has been executed and you can see which parts of your software remain untested. After instrumenting your code and running your tests, a report is generated allowing you to view information coverage figures from a project level right down to the individual line of code. This process is called 'code coverage'.

http://jcoverage.com/products/jcoverage-gpl.html

JBlanket

JBlanket is a tool for assessing and improving method coverage of unit test cases. It is integrated with JUnit and Ant.

http://csdl.ics.hawaii.edu/Tools/JBlanket/