unitcover: a NetBeans code coverage plugin based on EMMA

Vlad Roubtsov — Thu, 24 Aug 2006 16:24:46 -0000

There is a new open-source plugin for NetBeans for coverage visualization, based on EMMA: https://unitcover.dev.java.net/

The plugin binaries are available at
https://unitcover.dev.java.net/downloads/binaries.zip
and will also be published on the nbextras.org site.

EMMA ships with IntelliJ 6.0

Vlad Roubtsov — Sun, 30 Jul 2006 19:01:38 -0000

Pretty cool that we are integrated into one of the best IDEs around.

http://www.jetbrains.com/idea/docs/IDEA60ReviewerGuide.pdf
http://blogs.jetbrains.com/idea/2006/07/code-coverage/

Erik Beijnoff and Felipe Leme join EMMA

Vlad Roubtsov — Sat, 21 Jan 2006 14:54:09 -0000

Erik Beijnoff and Felipe Leme join the team and add years of combined Java experience to the team. We expect that their initial contribution will be an Eclipse plugin for EMMA.

Maven EMMA Plugin Rewrite Released

Vlad Roubtsov — Sat, 30 Jul 2005 18:01:29 -0000

A from-scratch rewrite of the Maven EMMA plugin has been released. For details, see the Maven-generated site for the plugin: http://emma.sourceforge.net/maven-emma-plugin/

Please try it out and give me (Chad aka thewoolleyman) any feedback. It is now architected based on the Maven Clover plugin, which has been around for a while and seems to work well.

A couple of notes:

1.The maven documentation site is available here: http://emma.sourceforge.net/maven-emma-plugin/ I tried to do a thorough job on the docs, suggestions for improvement are welcome.

2. The plugin WILL be available on the central ibiblio repository, however the upload request has not yet been filled. Until then, it is available at a repository hosted on the EMMA website, here: http://emma.sourceforge.net/maven/emma/plugins/ . You can add this to your local repo list, or install it manually (instructions on plugin docs site above)

3. One of the major changes is to have the default behavior of the plugin NOT overwrite original classes with instrumented classes, which has been a request.

4. Everything should be completely configurable via plugin properties or the very-flexible standard EMMA property-specification mechanisms.

5. Installation is now much more standard, and the procedure is documented on the maven docs home page.

I've tested this some on local projects, and it works for me. If you want to run instrumented jars in a container, you will obviously need EMMA on your classpath, but for plain unit-test-time reporting on a simple non-container project, you should not need to explicitly add EMMA as a dependency.

Enjoy, and give my any feedback you have. Please use the sourceforge tools to report any known bugs or enhancement requests.

Thanks,
Chad

EMMA early access build 2.1.5320 available (new ctl tool)

Vlad Roubtsov — Wed, 22 Jun 2005 02:45:56 -0000

EMMA is a fast Java code coverage tool based on low overhead bytecode
instrumentation. It is designed to support large scale enterprise software
projects as well as agile personal software processes.

The most significant change in this v2.1 stable build update is the addition of a
new tool, ctl. This tool allows remote control over EMMA runtime. Several
control commands are currently implemented:
- download coverage data to a local file,
- remotely dump coverage data,
- reset coverage data in a remote JVM.

J2EE/application server users should find the new capability very useful,
since it is now possible to collect coverage data without a JVM exit, across
the network, and without having to deal with classloading problems in exit
hook threads that plagued v2.0.

Following the usual EMMA design, this functionality is exposed in equal
measure via a new command line tool and a new ANT task. Because this is an
early access build, the official documentation has not been updated yet
(this will happen when v2.1 releases). Until then, see the update below for
the new tool usage details.

************************************************
CUMULATIVE LIST OF IMPLEMENTED FEATURE REQUESTS:
************************************************

2.1.5320

977714 support runtime coverage data collection without a JVM exit
http://sf.net/tracker/index.php?func=detail&aid=977714&group_id=108932&atid=651900

1167510 reset coverage data
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=1167510

A new processor, CtlProcessor (used by a new 'emma ctl' command line
tool and a new <ctl> ANT task) can communicate with a JVM running
EMMA-instrumented classes via a TCP socket. On each invocation, the
processor dispatches a series of control commands such as
'coverage.get', 'coverage.dump', and 'coverage.reset', for example:

<emma>
<ctl connect="localhost:47653" >
<command name="coverage.get" args="mycoverage.ec" />
<command>coverage.reset</command> 
</ctl>
</emma>
or
java -cp ... emma ctl -connect localhost:47653 \ -command coverage.get,mycoverage.ec \ -command coverage.reset

This will download current coverage data from a JVM at a given TCP address
and save it into a local file 'mycoverage.ec', followed by a coverage reset.

The connection string above is in the form "host:port", where the host
defaults to 'localhost' and the port to 47653. Currently, there are
three commands with the following arguments:

coverage.get[,<output pathname>][,<merge>][,<disable exit hook>]
coverage.dump[,<output pathname>][,<merge>][,<disable exit hook>]
coverage.reset

The first one asks the server JVM to send its current coverage data to
the client ctl tool over the socket connection, the second one asks the
server JVM to dump coverage data on the *server* machine. Consequently,
the optional argument <pathname> (defaults to 'coverage.ec') is
interpreted either on the client or on the server machine, depending on
the command used (the two machines can even run different OSes). The
<merge> boolean flag has the usual semantics. Finally, the last argument
indicates whether to disable the usual dump-coverage-on-JVM-exit
behavior. Set it to 'false' if you want v2.0 behavior.

The last command will zero out all coverage numbers, except for class
coverage (class coverage corresponds to class loading, so it can't be
reset). Subsequent code execution will induce new coverage, of
course. Neither command suspends the JVM.

A command sequence can contain any number of commands. Note that in ANT,
<command name="coverage.get" args="mycoverage.ec" /> is the same as
<command>coverage.get,mycoverage.ec</command>. Use commas to delimit
arguments. If you want to skip an argument, use comma delimiters to
indicate that you are happy with its default, e.g,
<command>coverage.get,,,false</command>.

NOTE: 'coverage.reset' currently resets all static initializers. This is
not correct (since those can never execute again) and will be fixed in
the future.

This new functionality is controlled by a new set of EMMA properties:

rt.control: true
rt.control.host: localhost
rt.control.port: 47653

2.1.5214

974340 make concurrent output file writing safer
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=974340

v2.1 will default to using a machine-global mutex when writing to the
coverage output file. This mutex implementation is based on a UDP socket
and will work in any J2SE version. Locking behavior is controlled by a
new set of EMMA properties:

rt.filelock: true
rt.filelock.portbase: 59141
rt.filelock.maxtime: 120000
rt.filelock.retries: 11

File locking is enabled by default but can be disabled using
'rt.filelock' boolean property. The UDP port acquired is a sum of
'rt.filelockbase' and an offset (0-254) that is derived from the file's
canonical pathname. This ensures that concurrent JVMs writing to
*different* files are unlikely to serialize each other on the same
socket mutex.

'rt.filelock.maxtime' and 'rt.filelock.retries' specify for how long to
try getting the lock and in how many retry attempts, before erroring
out. The retry scheme is exponential backout.

2.1.5124

999764 'v'/'version' command line option
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=999764

The traditional -v|-version option is now accepted by all command line
tools, to help with issue submission.

977738 an option to auto-exclude empty classes
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=977738

v2.1 will default to automatically excluding all classes with no methods
(javac has a flaw whereby it will emit such classes for certain code
patterns). This behavior is controlled by a new boolean property
'instr.exclude_empty_classes' that defaults to 'true'. Because such
empty classes affect class coverage, users who wish to retain their
existing coverage numbers can turn this exclusion off. Note that all
other types of coverage are unaffected.

************************************************
CUMULATIVE LIST OF FIXED DEFECTS:
************************************************

2.1.5320

1222865 <filter file=.../> fails inside dirs with whitespace
http://sf.net/tracker/index.php?func=detail&aid=1222865&group_id=108932&atid=651897

2.1.5214

1189166 AIOOBE when handling report properties
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1189166

1015721 whitespace at end of property values
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1015721

1077741 report tool problem with "/"-prefixed report locations
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1077741

1002854 sourcepath and java file locations
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1002854

2.1.5124

(none)

EMMA bugfix release 2.0.5312 available

Vlad Roubtsov — Mon, 13 Jun 2005 01:30:37 -0000

EMMA is a fast Java code coverage tool based on low overhead bytecode
instrumentation. It is designed to support large scale enterprise software
projects as well as agile personal software processes.

Release build 2.0.5312 fixes a few minor bugs.

************************************************
LIST OF FIXED DEFECTS:
************************************************

2.0.5312

1189166 AIOOBE when handling report properties
http://sf.net/tracker/index.php?func=detail&aid=1189166&group_id=108932&atid=651897

988160 negative coverage numbers for very large projects
http://sf.net/tracker/index.php?func=detail&aid=988160&group_id=108932&atid=651897

EMMA early access build 2.1.5214 available

Vlad Roubtsov — Sat, 14 May 2005 18:50:22 -0000

EMMA is a fast Java code coverage tool based on low overhead bytecode
instrumentation. It is designed to support large scale enterprise software
projects as well as agile personal software processes.

This early access v2.1 build fixes an assortment of small bugs and
implements a feature that's been on frequently requested list for months.

************************************************
CUMULATIVE LIST OF IMPLEMENTED FEATURE REQUESTS:
************************************************

2.1.5214

974340 make concurrent output file writing safer
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=974340

v2.1 will default to using a machine-global mutex when writing to the
coverage output file. This mutex implementation is based on a UDP socket
and will work in any J2SE version. Locking behavior is controlled by a
new set of EMMA properties:

rt.filelock: true
rt.filelock.portbase: 59141
rt.filelock.maxtime: 120000
rt.filelock.retries: 11

File locking is enabled by default but can be disabled using
'rt.filelock' boolean property. The UDP port acquired is a sum of
'rt.filelockbase' and an offset (0-254) that is derived from the file's
canonical pathname. This ensures that concurrent JVMs writing to
*different* files are unlikely to serialize each other on the same
socket mutex.

'rt.filelock.maxtime' and 'rt.filelock.retries' specify for how long to
try getting the lock and in how many retry attempts, before erroring
out. The retry scheme is exponential backout.

2.1.5124

999764 'v'/'version' command line option
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=999764

The traditional -v|-version option is now accepted by all command line
tools, to help with issue submission.

977738 an option to auto-exclude empty classes
http://sf.net/tracker/?group_id=108932&atid=651900&func=detail&aid=977738

v2.1 will default to automatically excluding all classes with no methods
(javac has a flaw whereby it will emit such classes for certain code
patterns). This behavior is controlled by a new boolean property
'instr.exclude_empty_classes' that defaults to 'true'. Because such
empty classes affect class coverage, users who wish to retain their
existing coverage numbers can turn this exclusion off. Note that all
other types of coverage are unaffected.

************************************************
CUMULATIVE LIST OF FIXED DEFECTS:
************************************************

2.1.5214

1189166 AIOOBE when handling report properties
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1189166

1015721 whitespace at end of property values
http://sf.net/forum/forum.php?forum_id=386606

1077741 report tool problem with "/"-prefixed report locations
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1077741

1002854 sourcepath and java file locations
http://sf.net/tracker/?group_id=108932&atid=651897&func=detail&aid=1002854

2.1.5124

(none)

EMMA early access build 2.1.5124 available

Vlad Roubtsov — Sun, 24 Apr 2005 22:03:53 -0000

Stable build 2.1.5124 marks the beginning of v2.1 development.

FEATURE REQUESTS IMPLEMENTED:

999764 'v'/'version' command line option

The traditional -v|-version option is now accepted by all command line
tools, to help with issue submission.

977738 an option to auto-exclude empty classes

v2.1 will default to automatically excluding all classes with no methods
(javac has a flaw whereby it will emit such classes for certain code
patterns). This behavior is controlled by a new boolean property
'instr.exclude_empty_classes' that defaults to 'true'. Because such empty
classes affect class coverage, users who wish to retain their existing
coverage numbers can turn this exclusion off. Note that all other types of
coverage are unaffected.

Vlad Roubtsov

Chad Woolley joins EMMA

Vlad Roubtsov — Wed, 16 Mar 2005 02:57:22 -0000

Chad Woolley takes over Maven plugin work. Chad is already responsible for a set of improvements in the last two stable versions.

plugin 0.4 for Maven 1.0 available

Vlad Roubtsov — Sun, 13 Mar 2005 01:15:02 -0000

This is a bugfix/stable build of EMMA plugin for Maven 1.0.
Refer to version 0.2 release notes for installation and usage instructions.

DEFECTS FIXED IN v0.4:

1160469 maven emma:report goal doesn't work if tests not forked
1159069 emma.internal.enabled is not being set properly
1158200 Maven reports do not generate correctly after a clean

DEFECTS FIXED IN v0.3:

1144463 Source not visible in Maven Report

Recent posts to news

unitcover: a NetBeans code coverage plugin based on EMMA

EMMA ships with IntelliJ 6.0

Erik Beijnoff and Felipe Leme join EMMA

Maven EMMA Plugin Rewrite Released

EMMA early access build 2.1.5320 available (new ctl tool)

EMMA bugfix release 2.0.5312 available

EMMA early access build 2.1.5214 available

EMMA early access build 2.1.5124 available

Chad Woolley joins EMMA

plugin 0.4 for Maven 1.0 available