lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <hossman_luc...@fucit.org>
Subject Re: [jira] Updated: (LUCENE-721) Code coverage reports
Date Mon, 27 Nov 2006 05:51:00 GMT

: Here it is, Grant. This new patch uses Clover to generate code coverage
: reports. Simply add clover.jar to the ant classpath, do a "clean" and
: run the target "test". During compiling Clover will automatically
: instrument all classes under src/java.

haven't had a chance to look at the patch, but i have two questions baout
this:

1) is there any way to explicitly disable the instumentation (ie: with a
system property set in the build.properties, or on the command line) in
case people get into a situation where they are suspicious of hte
instrumentation and what to run the test without it?

2) what is the beahvior of the report generatation after a test failure?
DOes Clover know baout Ant failures?  would the report reflect the fact
that the tests failed in it's summary info?




-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message