Re: [Cobertura-devel] FW: Line/Branch Coverage is N/A

[Mark D. <ma...@ki...>]

I never responded to this, did I?

Re showing a warning when running cobertura-report on a data file without info
from the instrumentation step.
That's a good idea.  In fact, I think it'd be better if the cobertura-report
step failed altogether and didn't generate a report.  I'll try to do that for
Cobertura 1.5.

Re merging.
It's been broken for a little while.  It SHOULD be fixed in CVS, but I haven't
tried it personally.

-Mark


On Mon, 20 Jun 2005 21:09:47 -0600, Aronson, John wrote
> I answered my own question and I'll post it here in case somebody 
> does the same thing.
> 
> It was user error [of course]. My cobertura-instrument command did 
> not have a datafield attribute so it used the default path for the 
> serialization file. I was specifying the serialization file in the 
> junit and cobertura-report tasks. So naive users like myself should 
> be aware that the instrumentation task writes data to the 
> serialization in addition to generating the instrumented classes.
> 
> I'd like to request that the cobertura-report ant task emit a 
> warning when it reads a serialization file without the info from the 
> instrumentation step. That's a new? feature request.
> 
> Here's another question. The project I'm working on is broken up 
> into several directories, each directory has it's own ant build 
> script. With the junit and junitreport tasks I'm able to combine the 
> results across the project together and generate a combined report. 
> I tried to that with cobertura [using the merge command] but it 
> didn't work. Is that sort of usage supposed to work, or is it 
> strictly for combining different runs of the same set of tests like 
> it says in the docs?
> 
> John Aronson