cobertura-devel — General questions about using and developing Cobertura.

Re: [Cobertura-devel] 100% coverage but not all lines found

[John W. L. <Joh...@sa...>]

That is almost certainly a case where the process is not being pointed to the cobertura.ser file that was created during instrumentation.   Either the working directory of the process has to contain the cobertura.ser file, or the cobertura property has to be set that points to it.

From: Fabien Bataille [mailto:fba...@gm...]
Sent: Tuesday, April 12, 2011 8:42 AM
To: cobertura-devel
Subject: [Cobertura-devel] 100% coverage but not all lines found

Hi all,

I am getting 100% coverage when running a lots of automatic tests (~1500) on a big chunk of code. I found the following affirmation in the Cobertura FAQ

"Another common problem is that the cobertura.ser file is deleted, but the previously instrumented classes are not also deleted. Any time you delete your coverage data file you should also deleted all instrumented classes."

Does anyone have more information on that ? I understood that Cobertura is storing coverage data first in memory and then is flushing it to a file when the JVM stops. So what is the pb to keep already instrumented classes, as soon as the location of the cobertura.ser file does not change ? Is there dynamic information stored into these classes ?

As my platform is very huge instrumenting all classes at each run will last more than 24 hours, so I managed to create a cache for the instrumented jars in order not re-instrumenting them, as the cobertura.ser is always generating at the same location, and deleted between each run.

Thanks for your help !

Fabien

[Cobertura-devel] 100% coverage but not all lines found

[Fabien B. <fba...@gm...>]

*Hi all,

I am getting 100% coverage when running a lots of automatic tests (~1500) on
a big chunk of code. I found the following affirmation in the Cobertura FAQ

"Another common problem is that the cobertura.ser file is deleted, but the
previously instrumented classes are not also deleted. Any time you delete
your coverage data file you should also deleted all instrumented classes."

Does anyone have more information on that ? I understood that Cobertura is
storing coverage data first in memory and then is flushing it to a file when
the JVM stops. So what is the pb to keep already instrumented classes, as
soon as the location of the cobertura.ser file does not change ? Is there
dynamic information stored into these classes ?

As my platform is very huge instrumenting all classes at each run will last
more than 24 hours, so I managed to create a cache for the instrumented jars
in order not re-instrumenting them, as the cobertura.ser is always
generating at the same location, and deleted between each run.

Thanks for your help !

Fabien
*

Re: [Cobertura-devel] Cobertura “unable to locate file” problem

[fabien b. <fab...@al...>]

Hi,

I think you should try to use --destination for the source directory.

Fabien

On 04/11/2011 08:03 AM, lokendra singh wrote:
> Hi,
>
>
>     Please help me to understand what is wrong here?
>
>
>     I am using cobertura 1.9.4.1 for Java Code Coverage. I want to
>     attache the source file with HTML report, I am generating report
>     using the below command
>
>
>     cobertura-report.sh --format html --datafile
>     $COBERTURA_HOME/core/emscore.ser --basedir
>     $COBERTURA_HOME/core/src --destination $REPORT_DIR
>
>
>     HTML report generated successfully. Where I click on the file name
>     in HTML report, it is giving the below error:
>
>
>     "Unable to locate com/airvana/serverImpl/ObjectDao.java. Have you
>     specified the source directory?"
>
>
>     However I have the java source file at
>     $COBERTURA_HOME/core/src/com/airvana/serverImpl/ObjectDao.java
>
>
>     Thanks in advance.
>
>     Lokendra
>


-- 
Fabien Bataille
CTO/ASR
"Junior" Scrum Master
Route de Villejust
F-91620 Nozay
Tel:+33 130772750

[Cobertura-devel] Cobertura “unable to locate file” problem

[lokendra s. <lok...@ya...>]

Hi,


Please help me to understand what is wrong here? 


I am using cobertura 1.9.4.1 for Java Code Coverage. 
I want to attache the source file with HTML report, I am generating report using the below command 


cobertura-report.sh --format html --datafile
$COBERTURA_HOME/core/emscore.ser --basedir $COBERTURA_HOME/core/src
--destination $REPORT_DIR


HTML report generated successfully. Where I click on the file name in HTML report, it is giving the below error:


"Unable to locate com/airvana/serverImpl/ObjectDao.java. Have you specified the source directory?"


However I have the java source file at $COBERTURA_HOME/core/src/com/airvana/serverImpl/ObjectDao.java

            
Thanks in advance.

Lokendra

Re: [Cobertura-devel] Fwd: Re: Does the java source code need to be compiled with debug option ?

[Peter R. <pet...@gm...>]

When ant is used to compile java files
and if "debug" is not specified
ant will default to -g:none which disables line number generation (!)
- this is different from the javac command line, where the default is
-g:lines if
-g is not specified.

Peter

2011/4/10 Piotr Tabor <pi...@ta...>:
> The AFAIK the --debug (-g) flag does not help cobertura.
> Cobertura uses only the line-number information that is generated even
> without -g option.
> To generate the final report you need the *.ser file and the sources. With
> sources and line-numbers we can generate the complete report.
>
> Piotr
>
> 2011/3/28 Fabien Bataille <fba...@gm...>
>>
>> ---------- Forwarded message ----------
>> From: "Fabien Bataille" <fba...@gm...>
>> Date: Mar 28, 2011 2:55 PM
>> Subject: Re: [Cobertura-devel] Does the java source code need to be
>> compiled with debug option ?
>> To: "John W. Lewis" <Joh...@sa...>
>>
>> Hi,
>>
>> I have used a very basic helloWorld.java file with a if statement in it
>> and compiled it without -debug option, instrument it with cobertura, and I
>> get the coverage result in conformance with the test.
>>
>> class HelloWorld {
>>
>>         public HelloWorld() {
>>         }
>>
>>         static public void main(String[] args) {
>>
>>           for(int test = 0 ; test <1; test++) {
>>             if (test == 0) {
>>                 System.out.println("HelloWorld!");
>>             } else {
>>                 System.out.println("HelloWorld 2");
>>             }
>>           }
>>         HelloWorld hw = new HelloWorld();
>>         }
>> }
>>
>> Fabien
>>
>> On Mon, Mar 28, 2011 at 2:48 PM, John W. Lewis <Joh...@sa...>
>> wrote:
>> >
>> >
>> >
>> > That surpris...
>>
>>
>> ------------------------------------------------------------------------------
>> Create and publish websites with WebMatrix
>> Use the most popular FREE web apps or write code yourself;
>> WebMatrix provides all the features you need to develop and publish
>> your website. http://p.sf.net/sfu/ms-webmatrix-sf
>>
>> _______________________________________________
>> Cobertura-devel mailing list
>> Cob...@li...
>> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>>
>
>
>
> --
> Pozdrawiam,
> Piotr Tabor
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>
>

Re: [Cobertura-devel] Licensing

[Benson M. <bim...@gm...>]

Piotr,

I see your dilemma. You don't have all the copyright holders at hand,
so you're stuck with the license as it is.

I do have a bit of an idea for you.

Let's distinguish the license from the interpretation of the license.

Ignoring (for the moment) the confusing AL-for-ant business, what you
have is code under the GPL. However, most of the text on your
licensing page is an \interpretation/ of the GPL. In my view, you
could remove all of that and replace it with, more or less, "the
source code of Cobertura is licensed under the GPL version 2.0".

Really, nothing about the GPL forces you to publish that stuff about
exec-ing additional jvms. There are people out there who think that
the GPL can be enforced to impose restrictions like that, and other
people who don't. I don't think you'd be at any risk of misleading
anyone if you got rid of it.

Of course, you can leave the AL grant on the page as well, but I
wonder if you have documentation that all of the copyright holders
approved it? The issue being that since that grant isn't written in
terms of specific source files, it seems to either apply to all of the
code or none of the code. If it applies to all of the code, that there
are those who would say that the copyright holders granted an AL 1.1
licence to the whole thing if they granted anything at all.

I could write more about the legal issues at work here, but I hate to
waste your time.

In purely practical terms, it appears that the Codehaus people have
decided that they are willing to operate by more or less ignoring the
interpretative verbiage and just looking at the GPL and how maven
works. So we can keep the plugin in Codehaus and stop being all
tangled up with the 'ant' aspect of things.

--benson

Re: [Cobertura-devel] Licensing

[Piotr T. <pi...@ta...>]

Hi Benson,

I think that we  (with John) are currently the only two active developers of
Cobertura.
Personally I think that the problem is historical because of two reasons:
a) Cobertura is fork of GPL jcoverage branch and we can't just change the
license.
b) It is was clear what GPL means in terms of calling API. LGPL is more
clear in that area.

I think that every usage of Cobertura by caliing it's API is right and
should be allowed.
The license should only prohibit against embedding cobertura in commercial
tools.

The only thing I can personally offer is to donate code I authored to a new
project that don't have the historical problems:
Half a year ago I did a total rewrite of the whole core (instrumentation)
part of Cobertura. So I have a full right to that code and
I can publish it on AL/BSD license. There is the whole reporting stack
missing (but it's relatively simple and boring work).

Do you have any other idea what else can we do to help
maven-cobertura-plugin with that problem that does not cause violation of
the jcoverage license ?

Piotr

On Fri, Apr 1, 2011 at 3:17 PM, Benson Margulies <bim...@gm...>wrote:

> Dear Cobertura team,
>
> There is some uncertainty about the future of the
> cobertura-maven-plugin related to your licence page.
>
> The license page says that it grants an AL 1.1 license to 'use of the
> ant plugins.' However, it does not define 'the ant plugins.' Since
> they are in the same jars as the rest of cobertura, this is not
> self-evident.
>
> People working on the maven plugin in the past have interpreted this
> as 'calling functions from java packages with ant in their name and
> not calling functions from java packages that don't have ant in their
> names.'
>
> However, it seems to me to be equally plausible to imagine that the
> intent here is to require the *use of ant*. Period. In which case, the
> AL grant would not apply to a Maven plugin or anything else other than
> ant, itself. And, of course, intentions aren't what matters in the
> unlikely even of a legal set-to. Juries and judges reading your web
> page are what would matter, and there's no telling what they would
> read into the current wording.
>
> So, would you consider amending this to some other scheme like: 'We
> grant an apache license for use of cobertura via a plugin to any open
> source build tool?' Failing that, it would be better if the page made
> an unambiguous statement as to the meaning of 'use with ant'.
>
> I would also respectfully point out that I do not agree with your
> remarks about license compatibility. Nothing in the GPL or the AL
> prevents me as a *user* from combining ant (or maven) and cobertura in
> one JVM. The provisions of the GPL would apply if I created and
> published a work consisting of, or including, that combination. In my
> opinion, you could save your users some execution time by removing the
> remark about the jvm.
>
> So, to summarize, my personal belief is that anyone could create a
> maven plugin that calls your API, put a BSD license on the source, and
> publish it. Since the resulting plugin would not include any of your
> code, but merely state a dependency in its pom, there's not even
> aggregation, let alone derivation. However, it would be easier on the
> existing plugin team if you would relax the restriction as suggested
> above so that more cautious souls than I could participate.
>
>
> --benson margulies
>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>



-- 
Pozdrawiam,
Piotr Tabor

Re: [Cobertura-devel] Fwd: Re: Does the java source code need to be compiled with debug option ?

[Piotr T. <pi...@ta...>]

The AFAIK the --debug (-g) flag does not help cobertura.
Cobertura uses only the line-number information that is generated even
without -g option.
To generate the final report you need the *.ser file and the sources. With
sources and line-numbers we can generate the complete report.

Piotr

2011/3/28 Fabien Bataille <fba...@gm...>

> ---------- Forwarded message ----------
> From: "Fabien Bataille" <fba...@gm...>
> Date: Mar 28, 2011 2:55 PM
> Subject: Re: [Cobertura-devel] Does the java source code need to be
> compiled with debug option ?
> To: "John W. Lewis" <Joh...@sa...>
>
> Hi,
>
> I have used a very basic helloWorld.java file with a if statement in it and
> compiled it without -debug option, instrument it with cobertura, and I get
> the coverage result in conformance with the test.
>
> class HelloWorld {
>
>         public HelloWorld() {
>         }
>
>         static public void main(String[] args) {
>
>           for(int test = 0 ; test <1; test++) {
>             if (test == 0) {
>                 System.out.println("HelloWorld!");
>             } else {
>                 System.out.println("HelloWorld 2");
>             }
>           }
>         HelloWorld hw = new HelloWorld();
>         }
> }
>
> Fabien
>
>
>
> On Mon, Mar 28, 2011 at 2:48 PM, John W. Lewis <Joh...@sa...>
> wrote:
> >
> >
> >
> > That surpris...
>
>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and publish
> your website. http://p.sf.net/sfu/ms-webmatrix-sf
>
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>
>


-- 
Pozdrawiam,
Piotr Tabor

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

Hi,

We have solved the pb of the unfindable cobertura.properties during our
instrumented code execution.

On our platform we are using OSGI and thus the classloader by default is the
one of OSGI bundles dependence mechanism and so does not see the JVM main
classpath.

The solution to see cobertura.properties has been to change a line into
ConfigurationUtils.java method init. (Cobertura version 1.9.4.1)

old line:   URL url = this.getClass().getResource( RESOURCE );

new line: URL url = ClassLoader.getSystemClassLoader().getResource( RESOURCE
);

What is to be done is perhaps check first with the default classloader, and
if there no response, try the systemClassLoader.

Cheers,

Fabien

On Tue, Mar 29, 2011 at 7:07 PM, John W. Lewis <Joh...@sa...> wrote:

>
>
> Any specifics such as the command you used to kick off the process would be
> very helpful.   We need to be able to reproduce the behavior.
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 11:51 AM
>
> *To:* John W. Lewis
> *Cc:* cobertura-devel
> *Subject:* Re: [Cobertura-devel] cobertura.ser still created in current
> dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Since I backed up to version 1.9.4.1 instead of using the trunk version,
> everything is fine.
>
> If someone can have a look to what have changed in the new version about
> that.
>
> Cheers,
>
> Fabien
>
> On Tue, Mar 29, 2011 at 1:09 PM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> I’d pay close attention to how you are passing in the system property to
> the process.  It looks like you are using the right property.
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 6:08 AM
>
>
> *To:* John W. Lewis
> *Cc:* cobertura-devel
>
> *Subject:* Re: [Cobertura-devel] cobertura.ser still created in current
> dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> I simply launch the code, after having it instrumented and changing the JVM
> parameters to add cobertura.jar and its other librairies (jakarta oro,
> etc...).
>
> After shutdown I get back cobertura.ser and source code and generate the
> html report using cobertura scripts.
>
> On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> How are you starting the testing process if you are not using <junit>?
>
>
>
>
>
> No I am not using ant's junit.
>
> I was using the last version from the trunk, but I have now backup to the
> 1.9.4.1 version that I have recompiled and put the traces on.
>
> Fabien
>
> On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>
>
>
>
>
>
>

[Cobertura-devel] Licensing

[Benson M. <bim...@gm...>]

Dear Cobertura team,

There is some uncertainty about the future of the
cobertura-maven-plugin related to your licence page.

The license page says that it grants an AL 1.1 license to 'use of the
ant plugins.' However, it does not define 'the ant plugins.' Since
they are in the same jars as the rest of cobertura, this is not
self-evident.

People working on the maven plugin in the past have interpreted this
as 'calling functions from java packages with ant in their name and
not calling functions from java packages that don't have ant in their
names.'

However, it seems to me to be equally plausible to imagine that the
intent here is to require the *use of ant*. Period. In which case, the
AL grant would not apply to a Maven plugin or anything else other than
ant, itself. And, of course, intentions aren't what matters in the
unlikely even of a legal set-to. Juries and judges reading your web
page are what would matter, and there's no telling what they would
read into the current wording.

So, would you consider amending this to some other scheme like: 'We
grant an apache license for use of cobertura via a plugin to any open
source build tool?' Failing that, it would be better if the page made
an unambiguous statement as to the meaning of 'use with ant'.

I would also respectfully point out that I do not agree with your
remarks about license compatibility. Nothing in the GPL or the AL
prevents me as a *user* from combining ant (or maven) and cobertura in
one JVM. The provisions of the GPL would apply if I created and
published a work consisting of, or including, that combination. In my
opinion, you could save your users some execution time by removing the
remark about the jvm.

So, to summarize, my personal belief is that anyone could create a
maven plugin that calls your API, put a BSD license on the source, and
publish it. Since the resulting plugin would not include any of your
code, but merely state a dependency in its pom, there's not even
aggregation, let alone derivation. However, it would be easier on the
existing plugin team if you would relax the restriction as suggested
above so that more cautious souls than I could participate.


--benson margulies

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Steven C. <ste...@re...>]

I don't believe by default processed based tasks (I.E. spawning a new 
JVM in a JVM) will inherently pull all the arguments from the parent 
(maybe just the classpath). You need to tell the child JVM to pull from 
the parents JVM arguments.


On 3/30/2011 2:50 AM, Fabien Bataille wrote:
> Hi John,
>
> On one of my target, I still have the pb of the cobertura.ser not 
> found where it should even with version 1.9.4.1
>
> Based on the traces, the jvm option 
> -Dnet.sourceforge.cobertura.datafile=anotherPath is not seen sometime. 
> I have to check that all JVM are patched to be launched with this 
> option to be sure that during execution the file is read  and 
> generated at the right location.
>
> I need somemore time to isolate the pb and I will post again if I find 
> a problem with Cobertura.
>
> Cheers,
>
> Fabien

Email Disclaimer:
http://www.redprairie.com/emaildisclaimer/

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

Hi John,

On one of my target, I still have the pb of the cobertura.ser not found
where it should even with version 1.9.4.1

Based on the traces, the jvm option
-Dnet.sourceforge.cobertura.datafile=anotherPath
is not seen sometime. I have to check that all JVM are patched to be
launched with this option to be sure that during execution the file is read
and generated at the right location.

I need somemore time to isolate the pb and I will post again if I find a
problem with Cobertura.

Cheers,

Fabien


On Tue, Mar 29, 2011 at 7:07 PM, John W. Lewis <Joh...@sa...> wrote:

>
>
> Any specifics such as the command you used to kick off the process would be
> very helpful.   We need to be able to reproduce the behavior.
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 11:51 AM
>
> *To:* John W. Lewis
> *Cc:* cobertura-devel
> *Subject:* Re: [Cobertura-devel] cobertura.ser still created in current
> dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Since I backed up to version 1.9.4.1 instead of using the trunk version,
> everything is fine.
>
> If someone can have a look to what have changed in the new version about
> that.
>
> Cheers,
>
> Fabien
>
> On Tue, Mar 29, 2011 at 1:09 PM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> I’d pay close attention to how you are passing in the system property to
> the process.  It looks like you are using the right property.
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 6:08 AM
>
>
> *To:* John W. Lewis
> *Cc:* cobertura-devel
>
> *Subject:* Re: [Cobertura-devel] cobertura.ser still created in current
> dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> I simply launch the code, after having it instrumented and changing the JVM
> parameters to add cobertura.jar and its other librairies (jakarta oro,
> etc...).
>
> After shutdown I get back cobertura.ser and source code and generate the
> html report using cobertura scripts.
>
> On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> How are you starting the testing process if you are not using <junit>?
>
>
>
>
>
> No I am not using ant's junit.
>
> I was using the last version from the trunk, but I have now backup to the
> 1.9.4.1 version that I have recompiled and put the traces on.
>
> Fabien
>
> On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>
>
>
>
>
>
>

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[John W. L. <Joh...@sa...>]

Any specifics such as the command you used to kick off the process would be very helpful.   We need to be able to reproduce the behavior.

From: Fabien Bataille [mailto:fba...@gm...]
Sent: Tuesday, March 29, 2011 11:51 AM
To: John W. Lewis
Cc: cobertura-devel
Subject: Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

Since I backed up to version 1.9.4.1 instead of using the trunk version, everything is fine.

If someone can have a look to what have changed in the new version about that.

Cheers,

Fabien
On Tue, Mar 29, 2011 at 1:09 PM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

I'd pay close attention to how you are passing in the system property to the process.  It looks like you are using the right property.

From: Fabien Bataille [mailto:fba...@gm...<mailto:fba...@gm...>]
Sent: Tuesday, March 29, 2011 6:08 AM

To: John W. Lewis
Cc: cobertura-devel
Subject: Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

I simply launch the code, after having it instrumented and changing the JVM parameters to add cobertura.jar and its other librairies (jakarta oro, etc...).

After shutdown I get back cobertura.ser and source code and generate the html report using cobertura scripts.
On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

How are you starting the testing process if you are not using <junit>?


No I am not using ant's junit.

I was using the last version from the trunk, but I have now backup to the 1.9.4.1 version that I have recompiled and put the traces on.

Fabien
On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

That sounds right.   Are you using Ant's <junit>?

From: Fabien Bataille [mailto:fba...@gm...<mailto:fba...@gm...>]
Sent: Tuesday, March 29, 2011 3:24 AM
To: cobertura-devel
Subject: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

Hi,

During instrumentation and execution I add the java option -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to create and update the cobertura.ser file.

It seems that the option is well understood during the instrumentation, a cobertura.ser file is rightly created in the indicated file fullpath.

BUT when the instrumented code is executed with the same option passed to the JVM another cobertura.ser file is re-created in the current working dir.

Is it the right option to use ?

Thanks a lot for your help !

Fabien

[Cobertura-devel] Maven coverage from jar?

[David J. B. <Dav...@sa...>]

We're running Cobertura inside Maven inside Jenkins CI.

Is there any way to coerce cobertura:cobertura to instrument and report
on coverage for classes in a jar that are picked up via a Maven dependency?

We have split our code into separate projects (proj and proj.tests) but
we're not (yet) using Maven modules. We'd like to have Cobertura instrument and
report on coverage for the product code in proj (in a SNAPSHOT jar)
that proj.tests depends on, using <includes> and <exlcudes> in the proj.tests pom.xml
to specifify packages/classes in the proj jar.

It appears cobertura:cobertura only instruments .class files in
the current prjects' target/classes and/or target/test-classes
but not dependent jars. Is there any way to instrument and report
on coverage from classes in a dependent jar?

Note: we already use the dependency plugin to copy the jars from the
Maven repo locally into target/lib/jars so I have easy access
to the jar.

thanks,
djb

-- 
David J. Biesack, SAS
SAS Campus Dr. Cary, NC 27513
www.sas.com    (919) 531-7771

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

Since I backed up to version 1.9.4.1 instead of using the trunk version,
everything is fine.

If someone can have a look to what have changed in the new version about
that.

Cheers,

Fabien

On Tue, Mar 29, 2011 at 1:09 PM, John W. Lewis <Joh...@sa...> wrote:

>
>
> I’d pay close attention to how you are passing in the system property to
> the process.  It looks like you are using the right property.
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 6:08 AM
>
> *To:* John W. Lewis
> *Cc:* cobertura-devel
> *Subject:* Re: [Cobertura-devel] cobertura.ser still created in current
> dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> I simply launch the code, after having it instrumented and changing the JVM
> parameters to add cobertura.jar and its other librairies (jakarta oro,
> etc...).
>
> After shutdown I get back cobertura.ser and source code and generate the
> html report using cobertura scripts.
>
> On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> How are you starting the testing process if you are not using <junit>?
>
>
>
>
>
> No I am not using ant's junit.
>
> I was using the last version from the trunk, but I have now backup to the
> 1.9.4.1 version that I have recompiled and put the traces on.
>
> Fabien
>
> On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>
>
>
>
>

Re: [Cobertura-devel] Link between source class and test class

[John W. L. <Joh...@sa...>]

I'm not a maven expert, but I don't think it would be easy to do it.   I suppose you could create a pom.xml for each test.

-----Original Message-----
From: stlecho [mailto:st...@gm...] 
Sent: Tuesday, March 29, 2011 10:28 AM
To: cob...@li...
Subject: Re: [Cobertura-devel] Link between source class and test class


Could this "one-by-one" testing and reporting be automatised with the Maven plugin for Cobertura ?


John W. Lewis wrote:
> 
> 
> Not easily.   You would have to execute the tests one by one; run an xml
> report for each test; collect all the data for each test.
> 
> -----Original Message-----
> From: stlecho [mailto:st...@gm...]
> Sent: Tuesday, March 29, 2011 8:33 AM
> To: cob...@li...
> Subject: [Cobertura-devel] Link between source class and test class
> 
> 
> Hi,
> 
> Cobertura calculates the percentage of lines and branches covered for 
> each class. Our client would like to get a report on which test 
> classes/methods where used to calculate this percentage.
> 
> So for instance, he would like to know which tests have been executed 
> to cover lines 76-90 of 
> http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.inst
> rument.FirstPassMethodInstrumenter.html
> http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.inst
> rument.FirstPassMethodInstrumenter.html
> .
> 
> Is it possible to generate such a report with Cobertura ?
> 
> Regards, Stefan Lecho.
> --
> View this message in context:
> http://old.nabble.com/Link-between-source-class-and-test-class-tp31267
> 236p31267236.html Sent from the cobertura-devel mailing list archive 
> at Nabble.com.
> 
> 
> ----------------------------------------------------------------------
> -------- Enable your software for Intel(R) Active Management 
> Technology to meet the growing manageability and security demands of 
> your customers. Businesses are taking advantage of Intel(R) vPro (TM) 
> technology - will your software be a part of the solution? Download 
> the Intel(R) Manageability Checker today! 
> http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> 
> 
> 
> ----------------------------------------------------------------------
> -------- Enable your software for Intel(R) Active Management 
> Technology to meet the growing manageability and security demands of 
> your customers. Businesses are taking advantage of Intel(R) vPro (TM) 
> technology - will your software be a part of the solution? Download 
> the Intel(R) Manageability Checker today! 
> http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> 
> 

--
View this message in context: http://old.nabble.com/Link-between-source-class-and-test-class-tp31267236p31267956.html
Sent from the cobertura-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Cobertura-devel mailing list
Cob...@li...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel

Re: [Cobertura-devel] Link between source class and test class

[stlecho <st...@gm...>]

Could this "one-by-one" testing and reporting be automatised with the Maven
plugin for Cobertura ?


John W. Lewis wrote:
> 
> 
> Not easily.   You would have to execute the tests one by one; run an xml
> report for each test; collect all the data for each test.
> 
> -----Original Message-----
> From: stlecho [mailto:st...@gm...] 
> Sent: Tuesday, March 29, 2011 8:33 AM
> To: cob...@li...
> Subject: [Cobertura-devel] Link between source class and test class
> 
> 
> Hi,
> 
> Cobertura calculates the percentage of lines and branches covered for each
> class. Our client would like to get a report on which test classes/methods
> where used to calculate this percentage.
> 
> So for instance, he would like to know which tests have been executed to
> cover lines 76-90 of
> http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
> http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
> .
> 
> Is it possible to generate such a report with Cobertura ?
> 
> Regards, Stefan Lecho.
> --
> View this message in context:
> http://old.nabble.com/Link-between-source-class-and-test-class-tp31267236p31267236.html
> Sent from the cobertura-devel mailing list archive at Nabble.com.
> 
> 
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software 
> be a part of the solution? Download the Intel(R) Manageability Checker 
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> 
> 
> 
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software 
> be a part of the solution? Download the Intel(R) Manageability Checker 
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Link-between-source-class-and-test-class-tp31267236p31267956.html
Sent from the cobertura-devel mailing list archive at Nabble.com.

Re: [Cobertura-devel] Link between source class and test class

[John W. L. <Joh...@sa...>]

Not easily.   You would have to execute the tests one by one; run an xml report for each test; collect all the data for each test.

-----Original Message-----
From: stlecho [mailto:st...@gm...] 
Sent: Tuesday, March 29, 2011 8:33 AM
To: cob...@li...
Subject: [Cobertura-devel] Link between source class and test class


Hi,

Cobertura calculates the percentage of lines and branches covered for each class. Our client would like to get a report on which test classes/methods where used to calculate this percentage.

So for instance, he would like to know which tests have been executed to cover lines 76-90 of http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
.

Is it possible to generate such a report with Cobertura ?

Regards, Stefan Lecho.
--
View this message in context: http://old.nabble.com/Link-between-source-class-and-test-class-tp31267236p31267236.html
Sent from the cobertura-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Cobertura-devel mailing list
Cob...@li...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel

[Cobertura-devel] Link between source class and test class

[stlecho <st...@gm...>]

Hi,

Cobertura calculates the percentage of lines and branches covered for each
class. Our client would like to get a report on which test classes/methods
where used to calculate this percentage.

So for instance, he would like to know which tests have been executed to
cover lines 76-90 of 
http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
http://cobertura.sourceforge.net/sample/net.sourceforge.cobertura.instrument.FirstPassMethodInstrumenter.html
.

Is it possible to generate such a report with Cobertura ?

Regards, Stefan Lecho.
-- 
View this message in context: http://old.nabble.com/Link-between-source-class-and-test-class-tp31267236p31267236.html
Sent from the cobertura-devel mailing list archive at Nabble.com.

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[John W. L. <Joh...@sa...>]

I'd pay close attention to how you are passing in the system property to the process.  It looks like you are using the right property.

From: Fabien Bataille [mailto:fba...@gm...]
Sent: Tuesday, March 29, 2011 6:08 AM
To: John W. Lewis
Cc: cobertura-devel
Subject: Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

I simply launch the code, after having it instrumented and changing the JVM parameters to add cobertura.jar and its other librairies (jakarta oro, etc...).

After shutdown I get back cobertura.ser and source code and generate the html report using cobertura scripts.
On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

How are you starting the testing process if you are not using <junit>?


No I am not using ant's junit.

I was using the last version from the trunk, but I have now backup to the 1.9.4.1 version that I have recompiled and put the traces on.

Fabien
On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

That sounds right.   Are you using Ant's <junit>?

From: Fabien Bataille [mailto:fba...@gm...<mailto:fba...@gm...>]
Sent: Tuesday, March 29, 2011 3:24 AM
To: cobertura-devel
Subject: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

Hi,

During instrumentation and execution I add the java option -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to create and update the cobertura.ser file.

It seems that the option is well understood during the instrumentation, a cobertura.ser file is rightly created in the indicated file fullpath.

BUT when the instrumented code is executed with the same option passed to the JVM another cobertura.ser file is re-created in the current working dir.

Is it the right option to use ?

Thanks a lot for your help !

Fabien

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

I simply launch the code, after having it instrumented and changing the JVM
parameters to add cobertura.jar and its other librairies (jakarta oro,
etc...).

After shutdown I get back cobertura.ser and source code and generate the
html report using cobertura scripts.

On Tue, Mar 29, 2011 at 11:53 AM, John W. Lewis <Joh...@sa...> wrote:

>
>
> How are you starting the testing process if you are not using <junit>?
>
>
>
>
> No I am not using ant's junit.
>
> I was using the last version from the trunk, but I have now backup to the
> 1.9.4.1 version that I have recompiled and put the traces on.
>
> Fabien
>
> On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...>
> wrote:
>
>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>
>
>

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[John W. L. <Joh...@sa...>]

How are you starting the testing process if you are not using <junit>?

From: Fabien Bataille [mailto:fba...@gm...]
Sent: Tuesday, March 29, 2011 5:47 AM
To: John W. Lewis
Cc: cobertura-devel
Subject: Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

No I am not using ant's junit.

I was using the last version from the trunk, but I have now backup to the 1.9.4.1 version that I have recompiled and put the traces on.

Fabien
On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote:

That sounds right.   Are you using Ant's <junit>?

From: Fabien Bataille [mailto:fba...@gm...<mailto:fba...@gm...>]
Sent: Tuesday, March 29, 2011 3:24 AM
To: cobertura-devel
Subject: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

Hi,

During instrumentation and execution I add the java option -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to create and update the cobertura.ser file.

It seems that the option is well understood during the instrumentation, a cobertura.ser file is rightly created in the indicated file fullpath.

BUT when the instrumented code is executed with the same option passed to the JVM another cobertura.ser file is re-created in the current working dir.

Is it the right option to use ?

Thanks a lot for your help !

Fabien

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

No I am not using ant's junit.

I was using the last version from the trunk, but I have now backup to the
1.9.4.1 version that I have recompiled and put the traces on.

Fabien

On Tue, Mar 29, 2011 at 11:43 AM, John W. Lewis <Joh...@sa...> wrote:

>
>
> That sounds right.   Are you using Ant’s <junit>?
>
>
>
> *From:* Fabien Bataille [mailto:fba...@gm...]
> *Sent:* Tuesday, March 29, 2011 3:24 AM
> *To:* cobertura-devel
> *Subject:* [Cobertura-devel] cobertura.ser still created in current dir
> even with java -Dnet.sourceforge.cobertura.datafile=anotherPath
>
>
>
> Hi,
>
> During instrumentation and execution I add the java option
> -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
> create and update the cobertura.ser file.
>
> It seems that the option is well understood during the instrumentation, a
> cobertura.ser file is rightly created in the indicated file fullpath.
>
> BUT when the instrumented code is executed with the same option passed to
> the JVM another cobertura.ser file is re-created in the current working dir.
>
> Is it the right option to use ?
>
> Thanks a lot for your help !
>
> Fabien
>

Re: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[John W. L. <Joh...@sa...>]

That sounds right.   Are you using Ant's <junit>?

From: Fabien Bataille [mailto:fba...@gm...]
Sent: Tuesday, March 29, 2011 3:24 AM
To: cobertura-devel
Subject: [Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

Hi,

During instrumentation and execution I add the java option -Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to create and update the cobertura.ser file.

It seems that the option is well understood during the instrumentation, a cobertura.ser file is rightly created in the indicated file fullpath.

BUT when the instrumented code is executed with the same option passed to the JVM another cobertura.ser file is re-created in the current working dir.

Is it the right option to use ?

Thanks a lot for your help !

Fabien

[Cobertura-devel] cobertura.ser still created in current dir even with java -Dnet.sourceforge.cobertura.datafile=anotherPath

[Fabien B. <fba...@gm...>]

Hi,

During instrumentation and execution I add the java option
-Dnet.sourceforge.cobertura.datafile=/tmp/cobertura.ser to indicate where to
create and update the cobertura.ser file.

It seems that the option is well understood during the instrumentation, a
cobertura.ser file is rightly created in the indicated file fullpath.

BUT when the instrumented code is executed with the same option passed to
the JVM another cobertura.ser file is re-created in the current working dir.

Is it the right option to use ?

Thanks a lot for your help !

Fabien