Re: [jira] Updated: (HADOOP-1496) Test coverage target in build files using emma

[Nigel Daley <nd...@yahoo-inc.com>]

Thanks Simon for the clover patch.  However, I'm a little confused  
how this is supposed to work.  Doesn't the clover.jar need to be in  
the test's classpath?  I don't see this happening in this patch, nor  
do I see it happening in Lucene's build.xml or common-build.xml.   
Does this patch assume the clover.jar is copied somewhere (like the  
lib directory) before running the tests?


On Jun 27, 2007, at 1:57 PM, Simon Willnauer (JIRA) wrote:

>
>      [ https://issues.apache.org/jira/browse/HADOOP-1496? 
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Simon Willnauer updated HADOOP-1496:
> ------------------------------------
>
>     Attachment: hadoop_clover.patch
>
> Clover integration into Hadoop.
>
> I added the clover report task to the build.xml.
> We did that in the Lucene project a while ago and I had to do it  
> for work anyway so I added the tasks to the hadoop project as well.
>
> To generate the reports the clover.jar an clover.license from the  
> "commiter" repository must be available on the ANT Path.
> I had problems with the jar file located in the apache repository   
> so I use the current version from the cenqua website (http:// 
> www.cenqua.com/download.jspa - clover for ant-1.3.13)
>
> I created the reports running:
>
> ant  -Drun.clover=true clean test generate-clover-reports
>
>
>
>> Test coverage target in build files using emma
>> ----------------------------------------------
>>
>>                 Key: HADOOP-1496
>>                 URL: https://issues.apache.org/jira/browse/ 
>> HADOOP-1496
>>             Project: Hadoop
>>          Issue Type: Improvement
>>          Components: build
>>         Environment: all
>>            Reporter: woyg
>>            Priority: Minor
>>         Attachments: emma.tgz, hadoop_clover.patch,  
>> patch.emma.txt, patch.emma.txt.2
>>
>>
>> Test coverage targets for Hadoop using emma.
>> Test coverage will help in identifying the components which are  
>> not poperly covered in tests and write test cases for it.
>> Emma (http://emma.sourceforge.net/) is a good tool for coverage.
>> If you have something else in mind u can suggest.
>> I have a patch ready with emma.
>
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>