Re: [Cobertura-devel] Branch Coverage Showing as NA

[karl f. <klj...@ho...>]

John,
Thanks.  I now know what I did wrong.  I delete the .ser file generated by the call to cobertura-instrument.sh, then ran my test.  When I run cobertura-report.sh on the .ser file created by the test it shows Branch Coverage as NA.  If I don't delete the .ser file things work fine. m
KarlFrom: Joh...@sa...
To: klj...@ho...; cob...@li...
Subject: RE: [Cobertura-devel] Branch Coverage Showing as NA
Date: Thu, 28 Apr 2011 20:36:25 +0000











 
That is odd behavior.  I am not sure what is going on.
 
Since you said your build tool puts the source and classes in different directories, you would have cobertura-instrument point to the classes and have cobertura-report
 point to the source.
 
Can I see your commands?
 
John
 
 


From: karl francis [mailto:klj...@ho...]


Sent: Thursday, April 28, 2011 11:07 AM

To: cob...@li...

Subject: [Cobertura-devel] Branch Coverage Showing as NA


 

When I instrument the code and the .java file and .class file are in the same directory I get branch coverage numbers in the report.


When I instrument the code and the .java file is NOT available, I don't get branch coverage numbers in the report.  My build tool puts the .class files in a different directory
 that the .java files.  Does cobertura-instrument.sh support specifying a source directory?  Why is the source needed for branch coverage numbers to be generated?


 


Thanks,


 


Karl