lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-721) Code coverage reports
Date Sun, 26 Nov 2006 03:34:03 GMT
     [ http://issues.apache.org/jira/browse/LUCENE-721?page=all ]

Michael Busch updated LUCENE-721:
---------------------------------

    Attachment: clover.patch

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. 

After the junit tests are done, execute the new target "generate-clover-reports". Clover will
generate the html report in build/test/clover/reports. 

Note: If clover.jar can not be found in the ant classpath then "test" will simply print an
info message, saying that code coverage reports are disabled, and exeute the junit tests like
it did before this patch.

> Code coverage reports
> ---------------------
>
>                 Key: LUCENE-721
>                 URL: http://issues.apache.org/jira/browse/LUCENE-721
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Other
>            Reporter: Michael Busch
>         Assigned To: Michael Busch
>            Priority: Minor
>         Attachments: clover.patch, code_coverage.patch, emma_report.zip
>
>
> Hi all,
> We should be able to measure the code coverage of our unit testcases. I believe it would
be very helpful for the committers, if they could verify before committing a patch if it does
not reduce the coverage. 
> Furthermore people could take a look in the code coverage reports to figure out where
work needs to be done, i. e. where additional testcases are neccessary. It would be nice if
we could add a page to the Lucene website showing the report, generated by the nightly build.
Maybe you could add that to your preview page (LUCENE-707), Grant?
> I attach a patch here that uses the tool EMMA to generate the code coverage reports.
EMMA is a very nice open-source tool released under the CPL (same license as junit). The patch
adds three targets to common-build.xml: 
> - emma-check: verifys if both emma.jar and emma_ant.jar are in the ant classpath 
> - emma-instrument: instruments the compiled code 
> - generate-emma-report: generates an html code coverage report 
> The following steps are neccessary in order to generate a code coverage report:
> - add emma.jar and emma_ant.jar to your ant classpath (download emma from http://emma.sourceforge.net/)
> - execute ant target 'emma-instrument' (depends on compile-test, so it will compile all
core and test classes)
> - execute ant target 'test' to run the unit tests
> - execute ant target 'generate-emma-report'
> To view the emma report open build/test/emma/index.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
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