You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
(66) |
Apr
(29) |
May
(85) |
Jun
(66) |
Jul
(24) |
Aug
(139) |
Sep
(72) |
Oct
(26) |
Nov
(142) |
Dec
(34) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(55) |
Feb
(72) |
Mar
(43) |
Apr
(60) |
May
(95) |
Jun
(22) |
Jul
(48) |
Aug
(17) |
Sep
(54) |
Oct
(30) |
Nov
(82) |
Dec
(17) |
2007 |
Jan
(23) |
Feb
(38) |
Mar
(46) |
Apr
(12) |
May
(77) |
Jun
(77) |
Jul
(94) |
Aug
(51) |
Sep
(38) |
Oct
(57) |
Nov
(39) |
Dec
(67) |
2008 |
Jan
(38) |
Feb
(56) |
Mar
(42) |
Apr
(46) |
May
(37) |
Jun
(43) |
Jul
(52) |
Aug
(22) |
Sep
(22) |
Oct
(34) |
Nov
(37) |
Dec
(29) |
2009 |
Jan
(27) |
Feb
(35) |
Mar
(67) |
Apr
(37) |
May
(31) |
Jun
(79) |
Jul
(71) |
Aug
(59) |
Sep
(31) |
Oct
(47) |
Nov
(36) |
Dec
(7) |
2010 |
Jan
(15) |
Feb
(87) |
Mar
(38) |
Apr
(33) |
May
(24) |
Jun
(47) |
Jul
(26) |
Aug
(28) |
Sep
(33) |
Oct
(13) |
Nov
(8) |
Dec
(36) |
2011 |
Jan
(32) |
Feb
(10) |
Mar
(29) |
Apr
(29) |
May
(17) |
Jun
(14) |
Jul
(33) |
Aug
(11) |
Sep
(7) |
Oct
(7) |
Nov
(6) |
Dec
(10) |
2012 |
Jan
(19) |
Feb
(12) |
Mar
(16) |
Apr
(6) |
May
(18) |
Jun
(18) |
Jul
(31) |
Aug
(25) |
Sep
|
Oct
(31) |
Nov
(21) |
Dec
(9) |
2013 |
Jan
(8) |
Feb
(16) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
(29) |
Jul
(29) |
Aug
|
Sep
(7) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
2014 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
(13) |
May
(8) |
Jun
(5) |
Jul
(2) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
|
Dec
(2) |
2015 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Brian D. <bri...@ya...> - 2005-03-09 21:05:15
|
Thanks for the suggestions! I'm made some progress but still not quite working for me. When I removed the original classes and run the unit tests I get a NoClassDefFoundError for any of the production classes. I am using Spring which loads the files up by specifying the full package and name of the applicationContext.xml. Spring is actually throwing the NoClassDefFoundError itself and can't seem to find the file. The file actually exists in the instrumented directory. I was wondering when the class does get instrumented does it change the package name or name of the class when it's running in the JVM. If that is the case that would explain why Spring can't find the class to load. Thanks! --- Mark Doliner <Mar...@sa...> wrote: > It sounds like you have a pretty good understanding of what should > be happening. I'm not actually sure if the file size of > cobertura.ser should grow... I can't think of why it would, but > from experience I think it does. The time stamp on the file would > definitely be changed. You could try removing the original classes > before running the tests, to be absolutely sure you're using the > instrumented classes. > > The cobertura.ser file is generally only written when the JVM > exists. I suppose it's possible that you run your tests, and then > the ser file is written, then maybe you run another test in a new > JVM and it overwrites the ser file. (That's something I'd like to > see fixed sometime, maybe for the next version.) > -Mark > > > > -----Original Message----- > > From: cob...@li... > > [mailto:cob...@li...] On > > Behalf Of Brian Doyle > > Sent: Wednesday, March 09, 2005 12:57 PM > > To: Cob...@li... > > Subject: [Cobertura-devel] 0% code coverage > > > > I'm attempting to use Cobertura for the first time and the report > > shows up as 0% coverage even though I have unit tests. I assume > > that the cobertura.ser file is suppose to grow as the unit test > are > > running? That file is created and it never changes in size. The > ant > > build is always in the same directory, running, compiling and > > creating reports and there's only one of those cobertura.ser > files. > > Also the classpath for the unit tests has the instrumented > classes as > > the first thing in the path. The instrumented classes is > populated > > with classes. Not sure what else to check here. Any ideas? > Thanks. > > > > > > Brian Doyle > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading > now. > http://ads.osdn.com/?ad_ide95&alloc_id396&op=click > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > Brian Doyle I don't know about ignorance, and I don't care about apathy, but I simply will not put up with intolerance! - Unknown |
From: Mark D. <Mar...@sa...> - 2005-03-09 19:29:20
|
It sounds like you have a pretty good understanding of what should be = happening. I'm not actually sure if the file size of cobertura.ser = should grow... I can't think of why it would, but from experience I = think it does. The time stamp on the file would definitely be changed. = You could try removing the original classes before running the tests, to = be absolutely sure you're using the instrumented classes. The cobertura.ser file is generally only written when the JVM exists. I = suppose it's possible that you run your tests, and then the ser file is = written, then maybe you run another test in a new JVM and it overwrites = the ser file. (That's something I'd like to see fixed sometime, maybe = for the next version.) -Mark > -----Original Message----- > From: cob...@li...=20 > [mailto:cob...@li...] On=20 > Behalf Of Brian Doyle > Sent: Wednesday, March 09, 2005 12:57 PM > To: Cob...@li... > Subject: [Cobertura-devel] 0% code coverage >=20 > I'm attempting to use Cobertura for the first time and the report > shows up as 0% coverage even though I have unit tests. I assume > that the cobertura.ser file is suppose to grow as the unit test are > running? That file is created and it never changes in size. The ant > build is always in the same directory, running, compiling and > creating reports and there's only one of those cobertura.ser files.=20 > Also the classpath for the unit tests has the instrumented classes as > the first thing in the path. The instrumented classes is populated > with classes. Not sure what else to check here. Any ideas? Thanks. > =20 >=20 > Brian Doyle |
From: Peter S. <psc...@ex...> - 2005-03-09 19:14:56
|
Brian, what kind of application are you trying to run Cobertura on? - application - applet - servlet - or any mix of the above? When I tried it on our web-application, all the classes that did not need the TomCat-container to be run had > 0% coverage. The classes which needed the TomCat-container had 0% coverage on them...but we are now fixing that (see previous posting on this list) Regards Peter ----- Original Message ----- From: "Brian Doyle" <bri...@ya...> To: <Cob...@li...> Sent: Wednesday, March 09, 2005 6:56 PM Subject: [mailinglists] [Cobertura-devel] 0% code coverage > I'm attempting to use Cobertura for the first time and the report > shows up as 0% coverage even though I have unit tests. I assume > that the cobertura.ser file is suppose to grow as the unit test are > running? That file is created and it never changes in size. The ant > build is always in the same directory, running, compiling and > creating reports and there's only one of those cobertura.ser files. > Also the classpath for the unit tests has the instrumented classes as > the first thing in the path. The instrumented classes is populated > with classes. Not sure what else to check here. Any ideas? Thanks. > > > Brian Doyle > > I don't know about ignorance, and I don't care about apathy, but I simply will not put up with intolerance! - Unknown > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
From: Brian D. <bri...@ya...> - 2005-03-09 17:56:51
|
I'm attempting to use Cobertura for the first time and the report shows up as 0% coverage even though I have unit tests. I assume that the cobertura.ser file is suppose to grow as the unit test are running? That file is created and it never changes in size. The ant build is always in the same directory, running, compiling and creating reports and there's only one of those cobertura.ser files. Also the classpath for the unit tests has the instrumented classes as the first thing in the path. The instrumented classes is populated with classes. Not sure what else to check here. Any ideas? Thanks. Brian Doyle I don't know about ignorance, and I don't care about apathy, but I simply will not put up with intolerance! - Unknown |
From: Mark D. <the...@us...> - 2005-03-08 17:35:56
|
Should we get rid of the unmarshaller in net.sourceforge.cobertura.reports and just access the CoverageData directly? Jeremy, you metnioned this a few days ago, and I think I agree. Originally the unmarshaller was supposed to convert the coverage data into a form that was easier to work with, but I don't think this benefit outweights the slowdown it takes to convert all the coverage data from one format to another. We would probably need to change the CoverageData class a little bit to do everything the Clazz and Package classes do. And I was thinking it might be a good idea to separate the classes that instrument the bytecode from the classes that keep track of the coverage data. Any thoughts? -Mark |
From: Mark D. <the...@us...> - 2005-03-08 14:45:30
|
Cobertura 1.1 was released last night. You can get it from the download page: http://cobertura.sourceforge.net/download.html I'd also like to welcome our first new developer, Jeremy Thomerson. Jeremy fixed a bug in the XML reports for 1.1, and also added the <package> elements. We hope he'll be doing many cool things in the future :-) -Mark |