Re: [Cobertura-devel] Having problems generating report, possible instrumentation problem as well

[Grzegorz L. <ha...@gm...>]

Hi

I tried it the way you specified and it worked for me. Yours
cobertura.ser looks ok. It seems that there is something wrong with
reporting process - but i cannot reproduce behaviour you experienced.
I will try to help you - and us to find a bug.

First
Could you create some empty directory and point cobertura to look for
sources there (using option -s) when using report generation?

Second could you use attached jar (modified.jar) instead of
cobertura.jar? I modified two files (HTMLReport and Util) to show much
more information about things that happen. I also set there reporting
level to debug. Could you run reporting of your simple case and send
as what was logged? Modified files are attached.

To increase the number of log messages in normal cobertura
distribution file you will have to edit cobertura.jar and in file
log4j.properties change debug level from WARN to DEBUG.

Here is SourceForge archive for list cobertura-devel:
https://sourceforge.net/mailarchive/forum.php?forum_id=44317

Thanks for comprehensive description!

Greetings
Grzegorz Lukasik 

On Apr 2, 2005 1:17 AM, Martha Yanez <my...@us...> wrote:
>  
> 
>  Hi, 
> I'm trying to run cobertura with a tiny test program and having problem
> generating a report. 
> This is program, class files and ser output   . 
>  
> Cobertura.jar is in my classpath and I run following reporting command after
> executing DateUtil. 
>  
> C:\buildSLM>java net.sourceforge.cobertura.reporting.Main 
> -o c:\buildSLM\build-dir\r2 -i c:\buildSLM\cobertura.ser -s c:\buildSLM -f
> html 
>  
> The report command never terminates and my machine hits 100% processing when
> viewed under Task Manager 
> Some report files (index.html, frame-classes.html, frame-classes-.html (not
> a dup), frame-packages.html and frame-summary.html)  are generated very
> quickly at the start and then nothing.   
>  
>  
> I started this small test case because I suspect I may have an
> instrumentation problem. I tried instrumenting some of my product files
> (switching from the Jcoverage statements to the Cobertura ones Grzegorz was
> kind enough to send me this morning). It seems to go fine but when I ran the
> product I did not see the Cobertura.ser file being updated.  Since my
> product environment is a bit complex, I wanted to make sure I could get the
> simple test case working first and the little bit the report shows does seem
> like the test case ran (80%) but then the report problem comes in. If I try
> the ser file from my product instrumentation, the same thing happens (no
> termination - showing 0 coverage) 
>  
> Any help appreciated since I have limited time to get this working... also
> is there a debug or additional logging function I can turn on for more info
> on program execution?   
> One last thing... is there a way to see past mailing list entries? I'm now
> getting new updates but can't find past questions and hate to bother you
> asking something again that's been answered.   Thanks! 
> 
>  Martha Yanez
>  (919) 224-1320 / 8-687-1320
>  New Notes id: Martha Yanez/Raleigh/IBM
>  my...@us...
>  
>  
>