Re: [cinjug-users] your comment is greately appreciated!

["Edward Sumerfield" <esumerfd@xxxxxxxxxxx>]

A couple of others:

http://www.jcoverage.com/ perform the same tasks as emma. Though I have just
migrated from jcoverage to emma, the only benefit that I found was that the
emma ant task is less suceptable to problems with massive numbers of
instrumented files.

The coolest coverage tools are IDE integrated tools that give you live
feedback after ever test you run. Clover, as James says, is the best tool
for the job if you can afford it. However, there is a tool called coverlips
which is an eclipse plugin that does the same thing, for free but not as
well. It has some compatibility problems with cglib versions and I have
problems with spring loading conflicts but I have had lots of success with
it for all the simple junit tests.

http://coverlipse.sourceforge.net/index.php

----- Original Message ----- 
From: "Prateek Negi" <prateek_n@xxxxxxxxx>
To: "Daniel YH. Cho" <young_0648@xxxxxxxxx>; <users@xxxxxxxxxx>
Sent: Thursday, March 23, 2006 9:57 AM
Subject: Re: [cinjug-users] your comment is greately appreciated!


> It's Cobertura.
>
> http://cobertura.sourceforge.net/
>
> --- "Daniel YH. Cho" <young_0648@xxxxxxxxx> wrote:
>
> > What would be the best practice or any tools that I
> > could benefit from when I need to resolve the
> > followings?
> >
> > 1. Helping testers ensure they have been making
> > through all the code paths with their test cases.
> > 2. Helping us ensure that our unit tests have
> > completed coverage, and making the process more
> > measurable.
> > 3. Figuring out if there is "dead" code that we can
> > remove to reduce our rebase / rebuild turnaround
> > times.
> >
> > any suggestions?
> > Thanks.
> >
> > Daniel.