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 Tue, 21 Nov 2006 07:12:03 GMT
     [ http://issues.apache.org/jira/browse/LUCENE-721?page=all ]

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

    Attachment: emma_report.zip

I attach a code coverage report of the current HEAD (revision: 477535), so people can check
out how a report looks like. 

The current code coverage looks not bad: 77% of the code lines are being tested by our unit
tests. However, the coverage is not perfect: e. g. the PorterStemmer or IndexWriter.addIndexes(IndexReader[])
are not tested at all.

> 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
>            Priority: Minor
>         Attachments: 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