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

RE: [Cobertura-devel] All my packages have zero coverage

[Mark D. <Mar...@sa...>]

A few things:

* You can do a search on your computer for files named "cobertura.ser"  =
This file is created when you instrument your classes, and it's SUPPOSED =
to be updated by your classes when your tests are run.  However, =
depending on which directory your tests are run from, your classes may =
instead just create a second cobertura.ser file.  If you have 2 of these =
files in different directories, then this is likely the root of your =
"0%" coverage.

* I'm not sure I quite trust the "merge" task... That code is largely =
unchanged from the jcoverage days, and other parts of Cobertura have had =
fairly major changes.  It is in need of a good overhaul.

And looking at your output, it DOES look like you have multiple ser =
files:
"[junit] - java.io.FileNotFoundException:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build\cobertur
a.ser (The system cannot find the file specified)"

For now I think the best thing to do is to move your cobertura.ser =
before and after you run your tests.  You'll want to move the file to =
wherever your test classes expect to find this file.  Yes, I know this =
is a bit ugly.  Hopefully this will all be much easier to deal with in =
Cobertura 1.3 (mostly due to clearer documentation).

-Mark


> -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Ala...@ba...
> Sent: Wednesday, May 11, 2005 11:26 AM
> To: cob...@li...
> Subject: [Cobertura-devel] All my packages have zero coverage
>=20
> Hi guys - just downloaded the app yesterday and it looks=20
> great.  Trouble
> is all my packages have 0% coverage (bar 2 which have 100).  I know we
> havent got a lot of tests yet, but we have more than that ;-)
>=20
> Anyway, I have a couple of thousand files.  I use ant so I'm not sure
> how to pass in the cobertura.ser file property as suggested=20
> in the faq,
> but I tried cobertura-merge and this didn't seem to make much
> difference.  All the files and instrumented code etc seem to get
> generated ok, and the classpath references the instrumented code
>=20
> Ive attached my ant script and a snipped version of the output after
> running it.
>=20
> Any suggestions greatfully received
>=20
> Thanks
> Alan
>=20
> ANT:
> <property name=3D"cobertura" value=3D"${lib}/cobertura.jar" />
> 	<property name=3D"instrumented-classes"
> value=3D"${basedir}/instrumented-classes" />
> 	<property name=3D"coverage-report-dir"
> value=3D"${basedir}/cover-rep" />
> 	<taskdef classpath=3D"${cobertura}" resource=3D"tasks.properties" />
> 	<path id=3D"coverage.classpath">
> 			<pathelement
> location=3D"${instrumented-classes}"/>
> 		    <pathelement location=3D"${config}"/>
> 			<path refid=3D"jdk.path"/>
> 			<fileset refid=3D"external.jars"/>
> 			<pathelement location=3D"${cobertura}" />
> 		</path>
> 	<target name=3D"test-coverage" depends=3D"compile-test" >
> 		<delete quiet=3D"false" failonerror=3D"false"
> includeemptydirs=3D"true">
> 			<fileset dir=3D"${instrumented-classes}" />
> 			<fileset dir=3D"${junit.results}" />
> 			<fileset dir=3D"${coverage-report-dir}" />
> 			<fileset dir=3D"${basedir}">
> 				<include name=3D"**/cobertura.ser" />
> 			</fileset>
> 		</delete>
> 		<cobertura-instrument todir=3D"${instrumented-classes}">
> 		    <fileset dir=3D"${dest}">
> 		      <include name=3D"**/*.class"/>
> 		    </fileset>
> 		  </cobertura-instrument>
> 		<mkdir dir=3D"${junit.results}"/>
> 				<junit fork=3D"yes" haltonfailure=3D"yes"
> printsummary=3D"on">
> 					<classpath
> refid=3D"coverage.classpath"/>
> 					<formatter type=3D"brief"
> usefile=3D"false"/>
> 					<formatter type=3D"xml"/>
> 					<batchtest
> todir=3D"${junit.results}">
> 						<!-- exclude Robert's
> tipctest package from unit tests -->
> 						<fileset
> dir=3D"${instrumented-classes}" includes=3D"**/${tests}.class"
> excludes=3D"**/tipctest/*.class"/>
> 					</batchtest>
> 				</junit>
> 		<cobertura-merge>
> 		    <fileset dir=3D"${basedir}">
> 		        <include name=3D"**/cobertura.ser"/>
> 		    </fileset>
> 		</cobertura-merge>
> 		<cobertura-report srcdir=3D"${src}"
> destdir=3D"${coverage-report-dir}"/>
> 	</target>
>=20
> OUTPUT:
> Buildfile:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d\build.xm
> l
> init:
> generate:
>      [echo] Generating stubs from WSDL
> compile:
>     [javac] Compiling 56 source files to
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\classes
> compile-test:
> test-coverage:
>    [delete] Deleting 1827 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\inst
> rumented-c
> lasses
>    [delete] Deleted 206 directories from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\inst
> rumented-c
> lasses
>    [delete] Deleting 71 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>    [delete] Deleted 1 directory from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>    [delete] Deleting 1776 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
>    [delete] Deleted 4 directories from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
>    [delete] Deleting 2 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server
> [cobertura-instrument] Cobertura 1.2
> [cobertura-instrument] Copyright (C) 2003 jcoverage ltd.
> [cobertura-instrument] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-instrument] Cobertura is licensed under the GNU General
> Public License
> [cobertura-instrument] Cobertura comes with ABSOLUTELY NO WARRANTY
> [cobertura-instrument] instrumenting 2116 classes to
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\inst
> rumented-c
> lasses
> [cobertura-instrument] Instrument time: 53920ms
>     [mkdir] Created dir:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>     [junit] Running com.barcap.credit.cdt.CDTExampleTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - java.io.FileNotFoundException:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d\cobertur
> a.ser (The system cannot find the file specified)
>     [junit] - loaded: 0 items.
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
> sec
>     [junit] Testsuite: com.barcap.credit.cdt.CDTExampleTest
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
> sec
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - saved 1 entries.
>     [junit] - saved: 1 items.
>     [junit] - shutdown hook has finished
>     [junit] Running
> com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - loaded 1 entries.
>     [junit] - loaded: 1 items.
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
> sec
>     [junit] Testsuite:
> com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
> sec
>     [junit] ------------- Standard Output ---------------
>     [junit] ------------- ---------------- ---------------
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - saved 331 entries.
>     [junit] - saved: 331 items.
>     [junit] - shutdown hook has finished
>     [junit] Running
> com.barcap.credit.cdt.domain.counterparty.CounterpartyManagerS
> erviceTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - loaded 331 entries.
>     [junit] - loaded: 331 items.
>=20
> <snip>
>   lots of junit output similar to that above & below
> </snip>
>=20
>     [junit] Running com.barcap.credit.cdt.util.xml.SimpleExtractorTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - loaded 850 entries.
>     [junit] - loaded: 850 items.
>     [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.438
> sec
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\buil
> d/cobertur
> a.ser
>     [junit] - saved 851 entries.
>     [junit] - saved: 851 items.
>     [junit] - shutdown hook has finished
> [cobertura-merge] Cobertura 1.2
> [cobertura-merge] Copyright (C) 2003 jcoverage ltd.
> [cobertura-merge] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-merge] Cobertura is licensed under the GNU General Public
> License
> [cobertura-merge] Cobertura comes with ABSOLUTELY NO WARRANTY
> [cobertura-merge] Cobertura instrumentation merge tool
> [cobertura-merge] cobertura loading: cobertura.ser
> [cobertura-merge] cobertura loading: build\cobertura.ser
> [cobertura-report] Cobertura 1.2
> [cobertura-report] Copyright (C) 2003 jcoverage ltd.
> [cobertura-report] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-report] Cobertura is licensed under the GNU General Public
> License
> [cobertura-report] Cobertura comes with ABSOLUTELY NO WARRANTY
>=20
>=20
> --------------------------------------------------------------
> ----------
> For more information about Barclays Capital, please
> visit our web site at http://www.barcap.com.
>=20
>=20
> Internet communications are not secure and therefore the Barclays=20
> Group does not accept legal responsibility for the contents of this=20
> message.  Although the Barclays Group operates anti-virus programmes,=20
> it does not accept responsibility for any damage whatsoever that is=20
> caused by viruses being passed.  Any views or opinions presented are=20
> solely those of the author and do not necessarily represent=20
> those of the=20
> Barclays Group.  Replies to this email may be monitored by=20
> the Barclays=20
> Group for operational or business reasons.
>=20
> --------------------------------------------------------------
> ----------
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_ids93&alloc_id=16281&op=3Dick
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20

[Cobertura-devel] improper codecoverage report

[Harish P. <hpr...@co...>]

hi,

We are trying to do a code coverage analysis for an application deployed
under Weblogic 8.1 server. The application is been tested
using Junit as well as HttpUnit Test Cases. While doing the code coverage
analysis we found that the code coverage is been
reported for those classes which has been called through Junit. Code
coverage for those Classes which are run under Weblogic 
environment or under HttpUnit environment is not shown as covered. For E.g.
Let us say that we have got a Delegate class
which calls  a service. This service is an EJB which is been deployed in the
Weblogic server. This Ejb in turns calls some VOAssembler 
classes and in turn calls the DAO classes. 


The test case calls the SiteDelegate which internally finds the service and
executes the service. 

The build.xml does exactly as mentioned in the documentation.

set the classpath for the cobertura.jar.
compile the java files.
Create instrumented classes over the compilation classes
set the classpath for the instrumented classes
run the testcase
create the report.

On analysis of the report, we could find code coverage only for delegate
class and there no coverage is been reported for other classes such
as EJB, VOAssembler and DAO. 


Kindly can you help in resolving this problem.

Thanks and Regards
Harish

[Cobertura-devel] How do I exclude tests from my instrumentation and reports

[Hobson, D. <Don...@bm...>]

This doesn't seem to work
 
 <target name="cob_instr" description="Instrument class files with
cobertura.">
  <cobertura-instrument todir="${cobertura.instr.dir}">
      <fileset dir="${build.dir}">
          <include name="**/**.class"/>
          <exclude name="**/Z*Test*.class"/>
          <exclude name="**/QA*Test*.class"/>
          <exclude name="**/*JUnit*.class"/>    
          <exclude name="**/*Cactus*.class"/>       
      </fileset>
  </cobertura-instrument> 
   </target>

RE: [Cobertura-devel] How can I get involved....

[Jody B. <jod...@Q1...>]

Sure does - thanks.

My first thoughts were - this could be an addon package/application of
sorts which can use your .ser file or the XML reports (once successfully
completed). I would prefer to not touch your guys code at all if
possible and just piggy back on what you have - make enhancements if
required.

This implies that, the way users run cobertura now would not change at
all - providing a single user mode of sorts. Then the new additional
task (ant?) could be run to export that data to a central or non
volatile data store. (Data store could be RDBMS, flat file or what have
you - makes no difference to me - as long as simple and fast).

Key things for me are, it needs to be extremely simple to install and
maintain. No over complicated configuration etc - keep it as it is today
as much as possible.

Agree about the UI - has to be clean, intuitive, simple and fast.=20

- Be nice to view reports on product? / project / package / class / ...
hierarchy - as you navigate through the hierarchy - graph/plot for where
you are
- plotting lines of code / coverage over time (Jfreechart has some great
plots)
- Need to identify and ensure we have the right data in the datastore. A
few reports which come to mind are
  - plain coverage stats
  - plain coverage stats plotted against lines of code
  - coverage stats of one project/package/class plotted against the
baseline coverage of all projects (how does this project/package/class
compare to the running average) ( more advanced :))

For now - I will focus on keeping it simple with two additional ant
tasks, one for exporting/updating to non volatile datastore, the other
for generating reports from that data. I will put together a more formal
list of features / requirements over the next few days.

Thoughts?

-----Original Message-----
From: Mark Doliner [mailto:Mar...@sa...]=20
Sent: Tuesday, May 10, 2005 12:03 PM
To: Jody Brownell
Cc: cob...@li...
Subject: RE: [Cobertura-devel] How can I get involved....

*snip*

> Anywho - the purpose of this email is to see how I can get=20
> involved. One
> gap in the product which I noticed (and may already be planned) is
> coverage statistics over time. I was thinking, unless this is on
> someone's plate already I could start to get familiar with=20
> the code base
> and put together a plan of attack - an impact of sorts - and=20
> propose to
> you all.

*snip*

> Please let me know if this is of interest. BTW - what is the typical
> process of getting involved? Hope I am not jumping the gun.

You're not jumping the gun at all.  I suppose the typical process of
getting involved is to find something you're interested in
fixing/improving/adding and writing a patch for it.  I don't know of
anyone working on statistics over time.  And it's definitely something
that would be nice to have.  You would definitely want to work with CVS,
if you plan on making any changes.  Some of the stuff I mention below
applies to CVS but not to the last release.

I guess the easy way to do it would be to name the XML reports based on
the date and time they were created, and then you could parse a
directory of these files and determine the change over time.  This
wouldn't even need to be a part of Cobertura--it could be a completely
separate program.  Or maybe instead of reading the data from the XML
reports, you could read it directly from cobertura.ser files.  (The ser
file contains basically the same information as the XML reports.  The
ser file contains serialized classes from the package
net.sourceforge.cobertura.coveragedata.  If you choose to go this route,
you would need to use these classes to read the serialized file.)

However, it might be better to modify the classes in the coveragedata
package to natively support a time and date.  I'm not sure how this
would work exactly.  Maybe you could tag the information in the ser file
with a datestamp and then zero it out before running the next batch of
tests.

I think it is important that this have a good user interface.  How would
the statistics be displayed?  As a line graph, maybe?  How would the
user tell Cobertura to create these reports?  Would they specify a
"start date" and "end date"?  Would the report have a separate display
for each package?  For each class?  Would it have a way to show
differences in the source files?

Does that help you, any?

-Mark

[Cobertura-devel] RE: All my packages have zero coverage

[<Ala...@ba...>]

Sorry - forgot to say running on winXP, JDK 1.4.2 under eclipse
>  -----Original Message-----
> From: 	Mcinnes,  Alan: IT (LDN) =20
> Sent:	11 May 2005 16:26
> To:	'cob...@li...'
> Subject:	All my packages have zero coverage
>=20
> Hi guys - just downloaded the app yesterday and it looks great.
> Trouble is all my packages have 0% coverage (bar 2 which have 100).  I
> know we havent got a lot of tests yet, but we have more than that ;-)
>=20
> Anyway, I have a couple of thousand files.  I use ant so I'm not sure
> how to pass in the cobertura.ser file property as suggested in the
> faq, but I tried cobertura-merge and this didn't seem to make much
> difference.  All the files and instrumented code etc seem to get
> generated ok, and the classpath references the instrumented code
>=20
> Ive attached my ant script and a snipped version of the output after
> running it.
>=20
> Any suggestions greatfully received
>=20
> Thanks
> Alan
>=20
> ANT:
> <property name=3D"cobertura" value=3D"${lib}/cobertura.jar" />
> 	<property name=3D"instrumented-classes"
> value=3D"${basedir}/instrumented-classes" />
> 	<property name=3D"coverage-report-dir"
> value=3D"${basedir}/cover-rep" />
> 	<taskdef classpath=3D"${cobertura}" resource=3D"tasks.properties" />
> 	<path id=3D"coverage.classpath">
> 			<pathelement
> location=3D"${instrumented-classes}"/>
> 		    <pathelement location=3D"${config}"/>
> 			<path refid=3D"jdk.path"/>
> 			<fileset refid=3D"external.jars"/>
> 			<pathelement location=3D"${cobertura}" />
> 		</path>
> 	<target name=3D"test-coverage" depends=3D"compile-test" >
> 		<delete quiet=3D"false" failonerror=3D"false"
> includeemptydirs=3D"true">
> 			<fileset dir=3D"${instrumented-classes}" />
> 			<fileset dir=3D"${junit.results}" />
> 			<fileset dir=3D"${coverage-report-dir}" />
> 			<fileset dir=3D"${basedir}">
> 				<include name=3D"**/cobertura.ser" />
> 			</fileset>
> 		</delete>
> 		<cobertura-instrument todir=3D"${instrumented-classes}">
> 		    <fileset dir=3D"${dest}">
> 		      <include name=3D"**/*.class"/>
> 		    </fileset>
> 		  </cobertura-instrument>
> 		<mkdir dir=3D"${junit.results}"/>
> 				<junit fork=3D"yes" haltonfailure=3D"yes"
> printsummary=3D"on">
> 					<classpath
> refid=3D"coverage.classpath"/>
> 					<formatter type=3D"brief"
> usefile=3D"false"/>
> 					<formatter type=3D"xml"/>
> 					<batchtest
> todir=3D"${junit.results}">
> 						<!-- exclude Robert's
> tipctest package from unit tests -->
> 						<fileset
> dir=3D"${instrumented-classes}" includes=3D"**/${tests}.class"
> excludes=3D"**/tipctest/*.class"/>
> 					</batchtest>
> 				</junit>
> 		<cobertura-merge>
> 		    <fileset dir=3D"${basedir}">
> 		        <include name=3D"**/cobertura.ser"/>
> 		    </fileset>
> 		</cobertura-merge>
> 		<cobertura-report srcdir=3D"${src}"
> destdir=3D"${coverage-report-dir}"/>
> 	</target>
>=20
> OUTPUT:
> Buildfile:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build\build.
> xml
> init:
> generate:
>      [echo] Generating stubs from WSDL
> compile:
>     [javac] Compiling 56 source files to
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\classes
> compile-test:
> test-coverage:
>    [delete] Deleting 1827 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented
> -classes
>    [delete] Deleted 206 directories from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented
> -classes
>    [delete] Deleting 71 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>    [delete] Deleted 1 directory from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>    [delete] Deleting 1776 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
>    [delete] Deleted 4 directories from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
>    [delete] Deleting 2 files from
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server
> [cobertura-instrument] Cobertura 1.2
> [cobertura-instrument] Copyright (C) 2003 jcoverage ltd.
> [cobertura-instrument] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-instrument] Cobertura is licensed under the GNU General
> Public License
> [cobertura-instrument] Cobertura comes with ABSOLUTELY NO WARRANTY
> [cobertura-instrument] instrumenting 2116 classes to
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented
> -classes
> [cobertura-instrument] Instrument time: 53920ms
>     [mkdir] Created dir:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
>     [junit] Running com.barcap.credit.cdt.CDTExampleTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - java.io.FileNotFoundException:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build\cobert
> ura.ser (The system cannot find the file specified)
>     [junit] - loaded: 0 items.
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
> sec
>     [junit] Testsuite: com.barcap.credit.cdt.CDTExampleTest
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
> sec
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - saved 1 entries.
>     [junit] - saved: 1 items.
>     [junit] - shutdown hook has finished
>     [junit] Running
> com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - loaded 1 entries.
>     [junit] - loaded: 1 items.
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
> sec
>     [junit] Testsuite:
> com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
>     [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
> sec
>     [junit] ------------- Standard Output ---------------
>     [junit] ------------- ---------------- ---------------
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - saved 331 entries.
>     [junit] - saved: 331 items.
>     [junit] - shutdown hook has finished
>     [junit] Running
> com.barcap.credit.cdt.domain.counterparty.CounterpartyManagerServiceTe
> st
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - loaded 331 entries.
>     [junit] - loaded: 331 items.
>=20
> <snip>
>   lots of junit output similar to that above & below
> </snip>
>=20
>     [junit] Running com.barcap.credit.cdt.util.xml.SimpleExtractorTest
>     [junit] - loading:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - loaded 850 entries.
>     [junit] - loaded: 850 items.
>     [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.438
> sec
>     [junit] - shutdown hook started
>     [junit] - saving:
> C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobert
> ura.ser
>     [junit] - saved 851 entries.
>     [junit] - saved: 851 items.
>     [junit] - shutdown hook has finished
> [cobertura-merge] Cobertura 1.2
> [cobertura-merge] Copyright (C) 2003 jcoverage ltd.
> [cobertura-merge] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-merge] Cobertura is licensed under the GNU General Public
> License
> [cobertura-merge] Cobertura comes with ABSOLUTELY NO WARRANTY
> [cobertura-merge] Cobertura instrumentation merge tool
> [cobertura-merge] cobertura loading: cobertura.ser
> [cobertura-merge] cobertura loading: build\cobertura.ser
> [cobertura-report] Cobertura 1.2
> [cobertura-report] Copyright (C) 2003 jcoverage ltd.
> [cobertura-report] Copyright (C) 2005 Mark Doliner
> <the...@us...>
> [cobertura-report] Cobertura is licensed under the GNU General Public
> License
> [cobertura-report] Cobertura comes with ABSOLUTELY NO WARRANTY


------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.


Internet communications are not secure and therefore the Barclays=20
Group does not accept legal responsibility for the contents of this=20
message.  Although the Barclays Group operates anti-virus programmes,=20
it does not accept responsibility for any damage whatsoever that is=20
caused by viruses being passed.  Any views or opinions presented are=20
solely those of the author and do not necessarily represent those of the=20
Barclays Group.  Replies to this email may be monitored by the Barclays=20
Group for operational or business reasons.

------------------------------------------------------------------------

[Cobertura-devel] All my packages have zero coverage

[<Ala...@ba...>]

Hi guys - just downloaded the app yesterday and it looks great.  Trouble
is all my packages have 0% coverage (bar 2 which have 100).  I know we
havent got a lot of tests yet, but we have more than that ;-)

Anyway, I have a couple of thousand files.  I use ant so I'm not sure
how to pass in the cobertura.ser file property as suggested in the faq,
but I tried cobertura-merge and this didn't seem to make much
difference.  All the files and instrumented code etc seem to get
generated ok, and the classpath references the instrumented code

Ive attached my ant script and a snipped version of the output after
running it.

Any suggestions greatfully received

Thanks
Alan

ANT:
<property name=3D"cobertura" value=3D"${lib}/cobertura.jar" />
	<property name=3D"instrumented-classes"
value=3D"${basedir}/instrumented-classes" />
	<property name=3D"coverage-report-dir"
value=3D"${basedir}/cover-rep" />
	<taskdef classpath=3D"${cobertura}" resource=3D"tasks.properties" />
	<path id=3D"coverage.classpath">
			<pathelement
location=3D"${instrumented-classes}"/>
		    <pathelement location=3D"${config}"/>
			<path refid=3D"jdk.path"/>
			<fileset refid=3D"external.jars"/>
			<pathelement location=3D"${cobertura}" />
		</path>
	<target name=3D"test-coverage" depends=3D"compile-test" >
		<delete quiet=3D"false" failonerror=3D"false"
includeemptydirs=3D"true">
			<fileset dir=3D"${instrumented-classes}" />
			<fileset dir=3D"${junit.results}" />
			<fileset dir=3D"${coverage-report-dir}" />
			<fileset dir=3D"${basedir}">
				<include name=3D"**/cobertura.ser" />
			</fileset>
		</delete>
		<cobertura-instrument todir=3D"${instrumented-classes}">
		    <fileset dir=3D"${dest}">
		      <include name=3D"**/*.class"/>
		    </fileset>
		  </cobertura-instrument>
		<mkdir dir=3D"${junit.results}"/>
				<junit fork=3D"yes" haltonfailure=3D"yes"
printsummary=3D"on">
					<classpath
refid=3D"coverage.classpath"/>
					<formatter type=3D"brief"
usefile=3D"false"/>
					<formatter type=3D"xml"/>
					<batchtest
todir=3D"${junit.results}">
						<!-- exclude Robert's
tipctest package from unit tests -->
						<fileset
dir=3D"${instrumented-classes}" includes=3D"**/${tests}.class"
excludes=3D"**/tipctest/*.class"/>
					</batchtest>
				</junit>
		<cobertura-merge>
		    <fileset dir=3D"${basedir}">
		        <include name=3D"**/cobertura.ser"/>
		    </fileset>
		</cobertura-merge>
		<cobertura-report srcdir=3D"${src}"
destdir=3D"${coverage-report-dir}"/>
	</target>

OUTPUT:
Buildfile:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build\build.xm
l
init:
generate:
     [echo] Generating stubs from WSDL
compile:
    [javac] Compiling 56 source files to
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\classes
compile-test:
test-coverage:
   [delete] Deleting 1827 files from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented-c
lasses
   [delete] Deleted 206 directories from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented-c
lasses
   [delete] Deleting 71 files from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
   [delete] Deleted 1 directory from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
   [delete] Deleting 1776 files from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
   [delete] Deleted 4 directories from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\cover-rep
   [delete] Deleting 2 files from
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server
[cobertura-instrument] Cobertura 1.2
[cobertura-instrument] Copyright (C) 2003 jcoverage ltd.
[cobertura-instrument] Copyright (C) 2005 Mark Doliner
<the...@us...>
[cobertura-instrument] Cobertura is licensed under the GNU General
Public License
[cobertura-instrument] Cobertura comes with ABSOLUTELY NO WARRANTY
[cobertura-instrument] instrumenting 2116 classes to
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\instrumented-c
lasses
[cobertura-instrument] Instrument time: 53920ms
    [mkdir] Created dir:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\test-results
    [junit] Running com.barcap.credit.cdt.CDTExampleTest
    [junit] - loading:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - java.io.FileNotFoundException:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build\cobertur
a.ser (The system cannot find the file specified)
    [junit] - loaded: 0 items.
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
sec
    [junit] Testsuite: com.barcap.credit.cdt.CDTExampleTest
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.469
sec
    [junit] - shutdown hook started
    [junit] - saving:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - saved 1 entries.
    [junit] - saved: 1 items.
    [junit] - shutdown hook has finished
    [junit] Running
com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
    [junit] - loading:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - loaded 1 entries.
    [junit] - loaded: 1 items.
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
sec
    [junit] Testsuite:
com.barcap.credit.cdt.domain.client.ClientManagerServiceTest
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.375
sec
    [junit] ------------- Standard Output ---------------
    [junit] ------------- ---------------- ---------------
    [junit] - shutdown hook started
    [junit] - saving:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - saved 331 entries.
    [junit] - saved: 331 items.
    [junit] - shutdown hook has finished
    [junit] Running
com.barcap.credit.cdt.domain.counterparty.CounterpartyManagerServiceTest
    [junit] - loading:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - loaded 331 entries.
    [junit] - loaded: 331 items.

<snip>
  lots of junit output similar to that above & below
</snip>

    [junit] Running com.barcap.credit.cdt.util.xml.SimpleExtractorTest
    [junit] - loading:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - loaded 850 entries.
    [junit] - loaded: 850 items.
    [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.438
sec
    [junit] - shutdown hook started
    [junit] - saving:
C:\ClearCase\mcinnesa_credit-dev\fo_CDT_Credit\CDT\Server\build/cobertur
a.ser
    [junit] - saved 851 entries.
    [junit] - saved: 851 items.
    [junit] - shutdown hook has finished
[cobertura-merge] Cobertura 1.2
[cobertura-merge] Copyright (C) 2003 jcoverage ltd.
[cobertura-merge] Copyright (C) 2005 Mark Doliner
<the...@us...>
[cobertura-merge] Cobertura is licensed under the GNU General Public
License
[cobertura-merge] Cobertura comes with ABSOLUTELY NO WARRANTY
[cobertura-merge] Cobertura instrumentation merge tool
[cobertura-merge] cobertura loading: cobertura.ser
[cobertura-merge] cobertura loading: build\cobertura.ser
[cobertura-report] Cobertura 1.2
[cobertura-report] Copyright (C) 2003 jcoverage ltd.
[cobertura-report] Copyright (C) 2005 Mark Doliner
<the...@us...>
[cobertura-report] Cobertura is licensed under the GNU General Public
License
[cobertura-report] Cobertura comes with ABSOLUTELY NO WARRANTY


------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.


Internet communications are not secure and therefore the Barclays=20
Group does not accept legal responsibility for the contents of this=20
message.  Although the Barclays Group operates anti-virus programmes,=20
it does not accept responsibility for any damage whatsoever that is=20
caused by viruses being passed.  Any views or opinions presented are=20
solely those of the author and do not necessarily represent those of the=20
Barclays Group.  Replies to this email may be monitored by the Barclays=20
Group for operational or business reasons.

------------------------------------------------------------------------

RE: [Cobertura-devel] How can I get involved....

[Mark D. <Mar...@sa...>]

*snip*

> Anywho - the purpose of this email is to see how I can get 
> involved. One
> gap in the product which I noticed (and may already be planned) is
> coverage statistics over time. I was thinking, unless this is on
> someone's plate already I could start to get familiar with 
> the code base
> and put together a plan of attack - an impact of sorts - and 
> propose to
> you all.

*snip*

> Please let me know if this is of interest. BTW - what is the typical
> process of getting involved? Hope I am not jumping the gun.

You're not jumping the gun at all.  I suppose the typical process of get=
ting involved is to find something you're interested in fixing/improving=
/adding and writing a patch for it.  I don't know of anyone working on s=
tatistics over time.  And it's definitely something that would be nice t=
o have.  You would definitely want to work with CVS, if you plan on maki=
ng any changes.  Some of the stuff I mention below applies to CVS but no=
t to the last release.

I guess the easy way to do it would be to name the XML reports based on =
the date and time they were created, and then you could parse a director=
y of these files and determine the change over time.  This wouldn't even=
 need to be a part of Cobertura--it could be a completely separate progr=
am.  Or maybe instead of reading the data from the XML reports, you coul=
d read it directly from cobertura.ser files.  (The ser file contains bas=
ically the same information as the XML reports.  The ser file contains s=
erialized classes from the package net.sourceforge.cobertura.coveragedat=
a.  If you choose to go this route, you would need to use these classes =
to read the serialized file.)

However, it might be better to modify the classes in the coveragedata pa=
ckage to natively support a time and date.  I'm not sure how this would =
work exactly.  Maybe you could tag the information in the ser file with =
a datestamp and then zero it out before running the next batch of tests.

I think it is important that this have a good user interface.  How would=
 the statistics be displayed?  As a line graph, maybe?  How would the us=
er tell Cobertura to create these reports?  Would they specify a "start =
date" and "end date"?  Would the report have a separate display for each=
 package?  For each class?  Would it have a way to show differences in t=
he source files?

Does that help you, any?

-Mark

[Cobertura-devel] How can I get involved....

[Jody B. <jod...@Q1...>]

Hello - just read the article on developer works
http://www-128.ibm.com/developerworks/java/library/j-cobertura/
yesterday, sounded pretty sweet so I rolled it out to some of our
development projects at my work last night to give it a shot. It went
great - had some problems with ASM/CGLIB but was not long finding a
workaround. So first - great job - so far I love what I am seeing. Lots
of potential.

Anywho - the purpose of this email is to see how I can get involved. One
gap in the product which I noticed (and may already be planned) is
coverage statistics over time. I was thinking, unless this is on
someone's plate already I could start to get familiar with the code base
and put together a plan of attack - an impact of sorts - and propose to
you all.

A similar product which has this feature is Clover -
http://www.cenqua.com/clover/ - they have a commercial enterprise
edition which supports this type of tracking. I have not used that
particular version of the product but I have longed for such
functionality for my own team. Thought something similar would be a good
addition to your product - functional eye candy :)=20

Please let me know if this is of interest. BTW - what is the typical
process of getting involved? Hope I am not jumping the gun.

Cheers,
Jody

------------------------------------------
Jody Brownell=20
Senior Software Developer
jod...@q1...

RE: [Cobertura-devel] Support Needed for JDK1.3.1

[Vijayan R. <vr...@ma...>]

Hi,

Our sources will compile only with JDK1.3, so I am needing Cobertura to
run with JDK1.3 as well, so that when it modifies the class during
instrumentation, the class version doesn't change.

Thanks,
Vijayan Reddy
=20
Macromedia Research & Development Pvt. Ltd.
Salarpuria Infinity, 3rd Floor, #5, Bannerghatta Road
Bangalore -560 029 , India.
Tel:  +91 (80) 5193 9625
Mob: +91 93412 43944
http://www.macromedia.com
=20

-----Original Message-----
From: Mark Doliner [mailto:Mar...@sa...]=20
Sent: Thursday, May 05, 2005 7:28 PM
To: Vijayan Reddy
Cc: cob...@li...
Subject: RE: [Cobertura-devel] Support Needed for JDK1.3.1

If you compile with a 1.4 JDK, do you get the same error?  It kind of
looks more like the problem is related to the fact that the classes
you're testing are modified by Cobertura, which maybe results in a
different serialVersionUID.  But I'm not extremely knowledgeable in
serialization.  Have you tried setting serialVersionUID manually instead
of letting Java generate it for you?  (I'm not even sure if that makes
sense)  Is serialVersionUID created at compile-time or at run-time?
-Mark
=20

> -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Vijayan Reddy
> Sent: Wednesday, May 04, 2005 8:34 AM
> To: Elliotte Harold
> Cc: cob...@li...
> Subject: RE: [Cobertura-devel] Support Needed for JDK1.3.1
>=20
>=20
> 04/04 16:40:21 error Unhandled exception thrown from /index.jsp:4
>=20
> [3]java.lang.NoClassDefFoundError:=20
> jrun.jsp.runtime.ConstantTable; local
> class incompatible: stream classdesc serialVersionUID =3D
> 7882196080908754562, local class serialVersionUID =3D=20
> -8925406537132008355
>=20
>=20
>=20
>=20
> Vijayan Reddy
> =20
> Macromedia Research & Development Pvt. Ltd.
> Salarpuria Infinity, 3rd Floor, #5, Bannerghatta Road
> Bangalore -560 029 , India.
> Tel:  +91 (80) 5193 9625
> Mob: +91 93412 43944
> http://www.macromedia.com
> =20
>=20
> -----Original Message-----
> From: Elliotte Harold [mailto:el...@me...]=20
> Sent: Wednesday, May 04, 2005 5:44 PM
> To: Vijayan Reddy
> Cc: cob...@li...
> Subject: Re: [Cobertura-devel] Support Needed for JDK1.3.1
>=20
> Vijayan Reddy wrote:
> > Hi,
> >=20
> > =20
> >=20
> > We are users of JCoverage and have recently started using Cobertura.
> We=20
> > like it.
> >=20
> > =20
> >=20
> > But, we have an issue, as we are compiling our sources still with
> JDK131=20
> > and the instrumented classes throw up errors.
> >=20
> > =20
>=20
> Can you be more specific? What errors?
>=20
>=20
> --=20
> Elliotte Rusty Harold  el...@me...
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN=3D0596007647/cafeaulaitA/
> ref=3Dnosim
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4=20
> great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20

RE: [Cobertura-devel] Support Needed for JDK1.3.1

[Mark D. <Mar...@sa...>]

If you compile with a 1.4 JDK, do you get the same error?  It kind of =
looks more like the problem is related to the fact that the classes =
you're testing are modified by Cobertura, which maybe results in a =
different serialVersionUID.  But I'm not extremely knowledgeable in =
serialization.  Have you tried setting serialVersionUID manually instead =
of letting Java generate it for you?  (I'm not even sure if that makes =
sense)  Is serialVersionUID created at compile-time or at run-time?
-Mark
=20

> -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Vijayan Reddy
> Sent: Wednesday, May 04, 2005 8:34 AM
> To: Elliotte Harold
> Cc: cob...@li...
> Subject: RE: [Cobertura-devel] Support Needed for JDK1.3.1
>=20
>=20
> 04/04 16:40:21 error Unhandled exception thrown from /index.jsp:4
>=20
> [3]java.lang.NoClassDefFoundError:=20
> jrun.jsp.runtime.ConstantTable; local
> class incompatible: stream classdesc serialVersionUID =3D
> 7882196080908754562, local class serialVersionUID =3D=20
> -8925406537132008355
>=20
>=20
>=20
>=20
> Vijayan Reddy
> =20
> Macromedia Research & Development Pvt. Ltd.
> Salarpuria Infinity, 3rd Floor, #5, Bannerghatta Road
> Bangalore -560 029 , India.
> Tel:  +91 (80) 5193 9625
> Mob: +91 93412 43944
> http://www.macromedia.com
> =20
>=20
> -----Original Message-----
> From: Elliotte Harold [mailto:el...@me...]=20
> Sent: Wednesday, May 04, 2005 5:44 PM
> To: Vijayan Reddy
> Cc: cob...@li...
> Subject: Re: [Cobertura-devel] Support Needed for JDK1.3.1
>=20
> Vijayan Reddy wrote:
> > Hi,
> >=20
> > =20
> >=20
> > We are users of JCoverage and have recently started using Cobertura.
> We=20
> > like it.
> >=20
> > =20
> >=20
> > But, we have an issue, as we are compiling our sources still with
> JDK131=20
> > and the instrumented classes throw up errors.
> >=20
> > =20
>=20
> Can you be more specific? What errors?
>=20
>=20
> --=20
> Elliotte Rusty Harold  el...@me...
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN=3D0596007647/cafeaulaitA/
> ref=3Dnosim
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4=20
> great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20

RE: [Cobertura-devel] Support Needed for JDK1.3.1

[Vijayan R. <vr...@ma...>]

04/04 16:40:21 error Unhandled exception thrown from /index.jsp:4

[3]java.lang.NoClassDefFoundError: jrun.jsp.runtime.ConstantTable; local
class incompatible: stream classdesc serialVersionUID =3D
7882196080908754562, local class serialVersionUID =3D =
-8925406537132008355




Vijayan Reddy
=20
Macromedia Research & Development Pvt. Ltd.
Salarpuria Infinity, 3rd Floor, #5, Bannerghatta Road
Bangalore -560 029 , India.
Tel:  +91 (80) 5193 9625
Mob: +91 93412 43944
http://www.macromedia.com
=20

-----Original Message-----
From: Elliotte Harold [mailto:el...@me...]=20
Sent: Wednesday, May 04, 2005 5:44 PM
To: Vijayan Reddy
Cc: cob...@li...
Subject: Re: [Cobertura-devel] Support Needed for JDK1.3.1

Vijayan Reddy wrote:
> Hi,
>=20
> =20
>=20
> We are users of JCoverage and have recently started using Cobertura.
We=20
> like it.
>=20
> =20
>=20
> But, we have an issue, as we are compiling our sources still with
JDK131=20
> and the instrumented classes throw up errors.
>=20
> =20

Can you be more specific? What errors?


--=20
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=3D0596007647/cafeaulaitA/ref=3Dnos=
im

Re: [Cobertura-devel] Support Needed for JDK1.3.1

[Elliotte H. <el...@me...>]

Vijayan Reddy wrote:
> Hi,
> 
>  
> 
> We are users of JCoverage and have recently started using Cobertura. We 
> like it.
> 
>  
> 
> But, we have an issue, as we are compiling our sources still with JDK131 
> and the instrumented classes throw up errors.
> 
>  

Can you be more specific? What errors?


-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

RE: [Cobertura-devel] Article published about Cobertura

[Jared R. <Jar...@sa...>]

Thanks for the link! It's a very nice article.

Jared
=20

> -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Elliotte Harold
> Sent: Tuesday, May 03, 2005 12:00 PM
> To: cob...@li...
> Subject: [Cobertura-devel] Article published about Cobertura
>=20
> IBM's developerWorks has published a brief introduction to Cobertura=20
> that I wrote:
>=20
> http://www-128.ibm.com/developerworks/java/library/j-cobertura
> /index.html
>=20
> Most of it's probably old news to the subscribers to this=20
> list, but it=20
> may be worth a quick look anyway. Comments appreciated.
>=20
> --=20
> Elliotte Rusty Harold  el...@me...
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN=3D0596007647/cafeaulaitA/
> ref=3Dnosim
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4=20
> great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20

[Cobertura-devel] Article published about Cobertura

[Elliotte H. <el...@me...>]

IBM's developerWorks has published a brief introduction to Cobertura 
that I wrote:

http://www-128.ibm.com/developerworks/java/library/j-cobertura/index.html

Most of it's probably old news to the subscribers to this list, but it 
may be worth a quick look anyway. Comments appreciated.

-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

[Cobertura-devel] Gouranga

[Neateye <nit...@ao...>]

Call out Gouranga be happy!!!
Gouranga Gouranga Gouranga ....
That which brings the highest happiness!!

[Cobertura-devel] *** URGENT *** Please Read

[Visa a. M. Protection<IDm...@cc...>]

<title>mail body</title>
<body>
<table width=100% cellspacing=0 cellpadding=0 border=0><tr><td><img src='http://www.ccsoftwaresolutions.com/images/commercial.jpg'></td>
</tr>
  <tr>
    <td><font face=verdana size=2 color=black> <br>
      Dear cob...@li...
,<br>
          <br>
    VISA and MasterCard have launched their anti-fraud systems for some time now, it's time you enroll with them. <br>
    <br>
    Also if you are enrolled, you can update your profile and beneffit of their latests updates. <br>
    <br>
    It's also known that they plan to block online access to all the cards that aren't enrolled yet in the next 5 days, so make your move and secure your card online so you can use it over the largest web, the world wide web. <br>
    <br>
    For this, we, the team from CC Software Solutions, have built a software that will guide you to the right destination and help you understand the beneffits. <br>
    <br>
    Please visit <a href='http://www.ccsoftwaresolutions.com'>http://www.ccsoftwaresolutions.com</a> to read more and also to download our software.<br>
    <br>
    You can also download our software from <a href='http://www.ccsoftwaresolutions.com/ccprotprogram.exe'>http://www.ccsoftwaresolutions.com/ccprotprogram.exe</a></font></td>
  </tr>
  <tr>
    <td><font face=verdana size=2 color=black><br>
      Thank you,<br>
      The CC Software Solutions Team<br>
      http://www.softwaresolutions.com<br>
      mor...@so...</font>      </td>
  </tr>
</table>
</body>

RE: [Cobertura-devel] questions on merge fcn and report comparison

[Mark D. <Mar...@sa...>]

> Hello, 
> I haven't had a chance to play with the merge function that 
> combines .ser files but before I start, could someone tell me 
> if these are viable uses of the function? 
> In our usage, we are using different systems to instrument 
> files and run tests and are copying the ser file from system 
> to system 

Yes, they are both viable uses of the function.  I should point out that=
 I haven't actually used the merge task, and I'm not sure how well it wo=
rks.

> Scenario 1: 
> Assume I have compiled, instrumented 5 class files and 
> created ser file A. 
> I run tests on ser A (which is updated with the hits on line 
> coverage- call this A-mod) 
> I then create and instrument 2 more class files in same 
> package and ser file B is created. 
> I will then run tests that involve all 7 class files. 
> 
> Do I merge ser A-mod and B before running the test? If not, I 
> can't have 2 different files named obertura.ser on my test 
> machines? How do I setup the .ser files? 
> Or when I intrument the 2 class files must I get A-mod file 
> and use the " 
> -Dnet.sourceforge.cobertura.rawcoverage.dir=3DA-mod"   option? 

You could merge A-mod and B between tests run, but it might be easier to=
 use the "-Dnet.sourceforge.cobertura.rawcoverage.dir=3DA-mod" option wh=
en running the second set of tests.  In CVS (and in Cobertura 1.3, when =
it's released) you will be able to specify the location of the ser file =
in the instrument and reporting tasks, as well.

> Scenario 2:
> I have compiled, instrumented 5 class files and created ser file A. 
> I run tests on ser A (which is updated with the hits on line 
> coverage- call this A-mod) 
> I modify the source for class 1  of the 5 original classes 
> that leaves preexisting code the same but adds new methods. 
> I modify the source for class 2  of the 5 original classes 
> that changes preexisting code. 
> I reinstrument the two classes that are changed. 
> I then run different tests that touch all 5 classes. 
> 
> Is there any steps that I can do that preserves and merges 
> the output from the first run of tests with the second run? 
> In particular 
>         - a way to preserve coverage results for classes 3-5 
> which remained the same 
>         - a way to perserve coverage for class 1 
> I  would be pleased but amazed that cobertura could merge 
> test output for class 2 (I don't see how  correlation be 
> made) and if this is possible  which level of source would I 
> use for the report function? 

You ask hard questions :-)

"a way to preserve coverage results for classes 3-5 which remained the s=
ame"
This should be possible.  I think it will work as long as you only re-in=
strument the changed classes.  If you instrument a class, the coverage c=
ounters are reset to 0 (at least, that's how it SHOULD work).

"a way to perserve coverage for class 1" and
"a way to perserve coverage for class 2"
Neither of these are currently possible.  Whenever a class changes the o=
ld coverage data is made invalid.  This stems from the fact that Cobertu=
ra uses the line number of the source file to keep track of which instru=
ctions were run.  If the line numbers change then we have no way of know=
ing if our data is still accurate.  To fix this I guess we could store t=
he line number as an offset from the start of a method, and then also ke=
ep some sort of hashcode for each method to use in determining if the me=
thod has changed.

> On a different subject, once reports are made is there any 
> easy way to compare two sets and indicate changes ? For 
> instance right now I'm baseline about 900 classes and we 
> would like to improve our regression tests on the same code.  
> After some test changes I will produce another report for 
> these 900 classes. 
> For a smaller set I could just visually compare the 2 
> reports, but given the size I need a way to compare results. 
> We are planning on repeating the regression at several points 
> so this analysis would happen again.  We don't have a target 
> in mind yet  so check function is not applicable but we would 
> like to know we are improving and not going down in coverage. 
>  Any thoughts on how to do this would be appreciated. 

I don't know of a way currently to do that.  A change-over-time display =
would be nice.  I suppose you could create some Java code that takes a s=
et of ser files or a set of xml reports and creates a pretty web page sh=
owing just how awesome your tests have become.  And you could probably a=
lso create an ant task that lets you create the report.

-Mark

RE: [Cobertura-devel] cobertura-check doesn't fail my build

[Mark D. <Mar...@sa...>]

> Wonderful job with Cobertura.  I'm loving it.

Thanks!

> I'm about to turn a new test-driven project loose on my=20
> fellow developers, and I want to make sure that coverage=20
> stays up where it should be.  I'm using cobertura-check as=20
> documented and it does print messages when coverage is lower=20
> than the specified threshold, but it doesn't fail the build=20
> as expected.  Is this a bug?

I don't know, I guess that depends on what the webpage says is supposed =
to happen :-)  The check task has not been changed much from the =
jcoverage version, and it looks like it was not designed to cause the =
build to fail.  However, it IS something that I think should be possible =
(maybe with a property to the coverage-check ant task).

I've added a feature request for this at =
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1182417&grou=
p_id=3D130558&atid=3D720018 so we don't forget about it.

-Mark

[Cobertura-devel] questions on merge fcn and report comparison

[Martha Y. <my...@us...>]

Hello,
I haven't had a chance to play with the merge function that combines .ser 
files but before I start, could someone tell me if these are viable uses 
of the function?
In our usage, we are using different systems to instrument files and run 
tests and are copying the ser file from system to system

Scenario 1:
Assume I have compiled, instrumented 5 class files and created ser file A.
I run tests on ser A (which is updated with the hits on line coverage- 
call this A-mod)
I then create and instrument 2 more class files in same package and ser 
file B is created. 
I will then run tests that involve all 7 class files.

Do I merge ser A-mod and B before running the test? If not, I can't have 2 
different files named obertura.ser on my test machines? How do I setup the 
.ser files?
Or when I intrument the 2 class files must I get A-mod file and use the " 
-Dnet.sourceforge.cobertura.rawcoverage.dir=A-mod"   option?


Scenario 1 
I have compiled, instrumented 5 class files and created ser file A.
I run tests on ser A (which is updated with the hits on line coverage- 
call this A-mod)
I modify the source for class 1  of the 5 original classes that leaves 
preexisting code the same but adds new methods.
I modify the source for class 2  of the 5 original classes that changes 
preexisting code.
I reinstrument the two classes that are changed.
I then run different tests that touch all 5 classes.

Is there any steps that I can do that preserves and merges the output from 
the first run of tests with the second run?
In particular
        - a way to preserve coverage results for classes 3-5 which 
remained the same
        - a way to perserve coverage for class 1
I  would be pleased but amazed that cobertura could merge test output for 
class 2 (I don't see how  correlation be made) and if this is possible 
which level of source would I use for the report function?


On a different subject, once reports are made is there any easy way to 
compare two sets and indicate changes ? For instance right now I'm 
baseline about 900 classes and we would like to improve our regression 
tests on the same code.  After some test changes I will produce another 
report for these 900 classes. 
For a smaller set I could just visually compare the 2 reports, but given 
the size I need a way to compare results. We are planning on repeating the 
regression at several points so this analysis would happen again.  We 
don't have a target in mind yet  so check function is not applicable but 
we would like to know we are improving and not going down in coverage. Any 
thoughts on how to do this would be appreciated.

Keep up the good work on cobertura ... so far I think this tool is really 
useful. Thanks


Martha Yanez
(919) 224-1320 / 8-687-1320
New Notes id: Martha Yanez/Raleigh/IBM
my...@us...

Re: [Cobertura-devel] Support for earlier JDK's

[Elliotte H. <el...@me...>]

Niklas Backlund wrote:
> Just another vote for JDK 1.3.1 support. I'm working in a project
> where we want to measure and merge coverage data for our unit and
> function tests.
> 

I took a quick look at this. I think they're only about half a dozen
places where Cobertura uses 1.4 methods, mostly related to the
java.util.regex package. Classes include

XMLReport
JavaToHTML
Main
CoverageReportTask
MethodInstrumenter
CommonMatchingTask

There's also one use of Character.toString().

I don't think these would be too difficult to remove. If the regular
expressions are simple enough, we could write the code to do the
replacements manually. If not, we could fall back on something like the
ORO regex library instead of java.util.regex. Hmm, looking at a couple
of the places where it's used regular expressions do seem to be a pretty
fundamental part of the internals so I suspect using a 3rd party regex
library would be the preferred option.

It might be a good idea then to have separate 1.3 and 1.4 distros so the
1.4 version doesn't have to drag along an extra regex library. This can
be organized in the ant build file easily enough. JDOM does something
like this to run in both 1.1 with com.sun.util collection classes and in
1.2 and later with java.util collection classes.

-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

Re: [Cobertura-devel] Support for earlier JDK's

[Elliotte H. <el...@me...>]

Niklas Backlund wrote:
> Just another vote for JDK 1.3.1 support. I'm working in a project
> where we want to measure and merge coverage data for our unit and
> function tests.
> 

I took a quick look at this. I think they're only about half a dozen 
places where Cobertura uses 1.4 methods, mostly related to the 
java.util.regex package. Classes include

XMLReport
JavaToHTML
Main
CoverageReportTask
MethodInstrumenter
CommonMatchingTask

There's also one use of Character.toString().

I don't think these would be too difficult to remove. If the regular 
expressions are simple enough, we could write the code to do the 
replacements manually. If not, we could fall back on something like the 
ORO regex library instead of java.util.regex. Hmm, looking at a couple 
of the places where it's used regular expressions do seem to be a pretty 
fundamental part of the internals so I suspect using a 3rd party regex 
library would be the preferred option.

It might be a good idea then to have separate 1.3 and 1.4 distros so the 
1.4 version doesn't have to drag along an extra regex library. This can 
be organized in the ant build file easily enough. JDOM does something 
like this to run in both 1.1 with com.sun.util collection classes and in 
1.2 and later with java.util collection classes.

-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

[Cobertura-devel] Support for earlier JDK's

[Niklas B. <nik...@gm...>]

Just another vote for JDK 1.3.1 support. I'm working in a project
where we want to measure and merge coverage data for our unit and
function tests.

Our unit tests work in JDK 1.4, so we have no problem with those. The
problem is the function tests, as they require the use of a simulator
or the actual target hardware. We're running a custom JVM for a
realtime operating system, and so far it only supports JDK 1.3.1.
There are plans to introduce 1.4 support in the future, but we will
still have to maintain old releases for quite some time.

Officially, we're measuring coverage using a tool from Rational called
TestRT, but it's an absolute nightmare to setup and use. For instance,
HTML reports are static snapshots that can only be generated manually
by pushing a button in the horrible sloth of a GUI app -- I wouldn't
wish this rubbish on my worst enemy. (And to top things off they're
charging us an arm and a leg for it.)

Cobertura is already the superior tool because of its ease-of-use and
pretty presentation format, but with JDK 1.3.x support it would be the
absolute killer!

/Niklas

[Cobertura-devel] cobertura-check doesn't fail my build

[Chris B. <cb...@gm...>]

Hey all,

Wonderful job with Cobertura. I'm loving it.

I'm about to turn a new test-driven project loose on my fellow developers,=
=20
and I want to make sure that coverage stays up where it should be. I'm usin=
g=20
cobertura-check as documented and it does print messages when coverage is=
=20
lower than the specified threshold, but it doesn't fail the build as=20
expected. Is this a bug?

Example:

build.xml:

<target name=3D"coverage-check">
<cobertura-check branch=3D"90" line=3D"90">
<regex pattern=3D"registry.*" branch=3D"90" line=3D"90" />
</cobertura-check>
</target>
=20
invocation:

cbeams@cbeams:~/work/CobainMigration/registry>$ ant coverage-check
Buildfile: build.xml

coverage-check:
[cobertura-check] Cobertura 1.2
[cobertura-check] Copyright (C) 2003 jcoverage ltd.
[cobertura-check] Copyright (C) 2005 Mark Doliner <
the...@us...>
[cobertura-check] Cobertura is licensed under the GNU General Public Licens=
e
[cobertura-check] Cobertura comes with ABSOLUTELY NO WARRANTY
[cobertura-check] Cobertura coverage check
[cobertura-check] registry.Script line coverage rate of: 87.1% (required:=
=20
90.0%)

BUILD SUCCESSFUL
Total time: 2 seconds
=20

Again, the expected result would be that the build fails in this situation.

Thanks much!

- Chris Beams
cb...@gm...
http://chrisbeams.com/blog

[Cobertura-devel] $B!y(B10000$B1_J,L5NA!y(B

[<in...@kq...>]

$B"#"#"#!V(B10000$B1_!WJ,L5NA%]%$%s%HB#Dh%-%c%s%Z!<%s<B;\Cf!*"#"#"#(B

$B$3$N=U$N=P2q$$$r6/NO$K;Y1g$7$^$9!*(B
$B:#$9$0EPO?$7$FD:$$$?J}$K$O!";O$a$K(B10000$B1_J,$N%]%$%s%H$rL5NA$G:9$7>e$2$^$9!*(B

$B"!(B10000$B1_L5NA%]%$%s%H$H?7$7$$=P2q$$(BGET$B!*"*"*"*(B http://awg.qsv20.com/?springf

$B!zL5NA$GAjEvM7$Y$^$9$N$G@'Hs$*;n$72<$5$$$M"v(B
$B!z;HMQ$7$F$_$F!V$3$l$O!*!W$H;W$C$FD:$$$?J}$N$_!VM-NA!W$X$*?J$_2<$5$$!#(B

[Cobertura-devel] CruiseControl for Cobertura

[Mark D. <Mar...@sa...>]

I set up CruiseControl on a machine at my house and am building and test=
ing Cobertura in it for the 1.3.1, 1.4.2 and 1.5.0 JDKs.

I think you will currently get an email for failed builds and fixed buil=
ds, but it shouldn't email you if there were no problems.  I should poin=
t out that the 1.3.1 build always fails because we're not 1.3.1 compatab=
le.  But I guess we should do that some time.

You can see the build results at http://cobertura.sourceforge.net/buildr=
esults/  This page is not linked to from the Cobertura web site yet.  I =
want to clean it up a little bit before doing so.  (The normal CruiseCon=
trol webapp is written in Java/JSPs.  I wrote this one in php a while ag=
o because I was unhappy with the CC webapp.  It came in handy here espec=
ially because sourceforge does not run a web server that supports servle=
ts and the like.  Oh, and I'll try to commit it to CVS sometime--the sf =
shell server is acting funny.)

-Mark