Menu
▾
▴
cobertura-devel — General questions about using and developing Cobertura.
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: Satyanarayana <rag...@ya...> - 2011-03-29 06:27:12
|
Including all others in the group
Satya
--- On Tue, 3/29/11, Satyanarayana <rag...@ya...> wrote:
From: Satyanarayana <rag...@ya...>
Subject: Re: [Cobertura-devel] Issue with latest cobertura code coverage metrics
To: "Piotr Tabor" <pi...@ta...>
Date: Tuesday, March 29, 2011, 11:55 AM
Hi Piotr,
With old version (Sample 1) - observe there is a huge difference in the count 806 in old version and 2844 in new version
----------------------
public void resetAll()
60 {
61 806 mCurrentPosition = 1;
62 806 mPageSize = 10;
63 806 mMaxRows = 500;
64 806 String maxRowStr = ConfigurationService.getApplicationConfiguration().getVariableString( "SYSTEM",
65 "maxPagingRows" );
66 806 if ( maxRowStr != null && maxRowStr.trim().length() > 0 )
67 {
68 try
69 {
70 0 mMaxRows = Integer.parseInt( maxRowStr );
71 }
72 0 catch ( NumberFormatException nfe )
73 {
74 0 LogService.getLogWriter().logWarning(
75 "maxPagingRows setting [" + maxRowStr + "] is not an Integer; ignoring." );
76 0 }
77 }
78 806 mSqlStatement = "";
79 806 mQueryValues = new ArrayList();
80 806 }
81
82 /**
83 * Checks for last page.
84 *
85 * @return true, if successful
86 */
With New Version (Sample 1)
--------------------------
59 public void resetAll()
60 {
61 2844 mCurrentPosition = 1;
62 2844 mPageSize = 10;
63 2844 mMaxRows = 500;
64 2844 String maxRowStr = ConfigurationService.getApplicationConfiguration().getVariableString( "SYSTEM",
65 "maxPagingRows" );
66 2844 if ( maxRowStr != null && maxRowStr.trim().length() > 0 )
67 {
68 try
69 {
70 0 mMaxRows = Integer.parseInt( maxRowStr );
71 }
72 0 catch ( NumberFormatException nfe )
73 {
74 0 LogService.getLogWriter().logWarning(
75 "maxPagingRows setting [" + maxRowStr + "] is not an Integer; ignoring." );
76 0 }
77 }
78 2844 mSqlStatement = "";
79 2844 mQueryValues = new ArrayList();
80 2844 }
81
82 /**
83 * Checks for last page.
84 *
85 * @return true, if successful
86 */
With Old Version (Sample 2) observe there is a huge difference in the count 38 in old version and 0 in new version
______________
public synchronized InputStream getResourceStream( String name ) throws ResourceNotFoundException
88 {
89 38 if ( name == null || name.length() == 0 )
90 {
91 0 throw new ResourceNotFoundException( "Need to specify a template name!" );
92 }
93 38 if ( getTemplates() != null )
94 {
95 38 Object aObject = mTemplates.get( name );
96 38 if ( aObject == null )
97 {
98 35 throw new ResourceNotFoundException( name + " not found" );
99 }
100 3 return ( ( Skin )aObject ).getHeaderTemplateInputStream();
101 }
102 else
103 {
104 0 throw new ResourceNotFoundException( name + " not found" );
105 }
106 }
With New Version (Sample 2)
--------------------------
87 public synchronized InputStream getResourceStream( String name ) throws ResourceNotFoundException
88 {
89 0 if ( name == null || name.length() == 0 )
90 {
91 0 throw new ResourceNotFoundException( "Need to specify a template name!" );
92 }
93 0 if ( getTemplates() != null )
94 {
95 0 Object aObject = mTemplates.get( name );
96 0 if ( aObject == null )
97 {
98 0 throw new ResourceNotFoundException( name + " not found" );
99 }
100 0 return ( ( Skin )aObject ).getHeaderTemplateInputStream();
101 }
102 else
103 {
104 0 throw new ResourceNotFoundException( name + " not found" );
105 }
106 }
Please let us know why the difference is coming ?
Satya
--- On Sat, 3/26/11, Piotr Tabor <pi...@ta...> wrote:
From: Piotr Tabor <pi...@ta...>
Subject: Re: [Cobertura-devel] Issue with latest cobertura code coverage metrics
To: "Satyanarayana" <rag...@ya...>
Date: Saturday, March 26, 2011, 1:17 AM
Hi Satya,
It is cost of progress. We are fixing bugs (and producing others) and hope that results returned by a newer version are better.
Could you identify a snippet of code that produced different results between the version. Then we would talk if it's a bug or feature.
Piotr
2011/3/25 Satyanarayana <rag...@ya...>
Hi Casey,
We have used Javc compiler in both the occasions (with old cobertura version and with new cobertura version), and the results are different.
Is there any change that is made to new version of cobertura ? Why are the results different when compared to old version ?
Satya
--- On Fri, 3/18/11, Casey McGinty <cas...@gm...> wrote:
From: Casey McGinty <cas...@gm...>
Subject: Re: [Cobertura-devel] Issue with latest cobertura code coverage metrics
To: "Satyanarayana" <rag...@ya...>
Cc: cob...@li...
Date: Friday, March 18, 2011, 12:54 AM
I noticed a similar problem. It was not related to change in Cobertura though so maybe your issue is different.
I determined that using Eclipse vs Javc compiler would give different results. When compiling with eclipse, multiline code would be counted as more than one statement. So you may want to check that. I would make sure you compile with javac and retest your result.
- Casey
2011/3/16 Satyanarayana <rag...@ya...>
Hi,
We are finding that the code coverage metrics reported by previous version and new version of cobertura (1.9.4.1) are inconsistent.
When we ran automation regression suite using previous version of cobertura we observed that the total code coverage % was reported as 31%.
Later when we took latest version of cobertura ((1.9.4.1) and when we ran the same automation regression suite as above, we are seeing that the total code coverage % metrics are reported as 11%
Regards,
Satya
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
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
--
Pozdrawiam,
Piotr Tabor
|
|
From: Fabien B. <fba...@gm...> - 2011-03-28 16:16:41
|
---------- 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...
|
|
From: John W. L. <Joh...@sa...> - 2011-03-28 12:48:15
|
That surprises me. You will see test results in a JUnit report, but I would think your coverage report would be empty. Basically, your tests would run the same as when Cobertura was not in the mix. John From: Fabien Bataille [mailto:fba...@gm...] Sent: Monday, March 28, 2011 8:44 AM To: cobertura-devel Subject: [Cobertura-devel] Does the java source code need to be compiled with debug option ? Hi, I noticed that even with a java byte code NOT COMPILED with the -debug option we are able to see some information about the test results. Is it ok or will I miss some information in the report ? Fabien |
|
From: Fabien B. <fba...@gm...> - 2011-03-28 12:43:56
|
Hi, I noticed that even with a java byte code NOT COMPILED with the -debug option we are able to see some information about the test results. Is it ok or will I miss some information in the report ? Fabien |
|
From: Casey M. <cas...@gm...> - 2011-03-25 19:29:26
|
On Fri, Mar 25, 2011 at 2:35 AM, Satyanarayana <rag...@ya...>wrote: > > > Why are the results different when compared to old version ? > * > * > > > When compiling with eclipse, multiline code would be counted as more than one statement. |
|
From: Satyanarayana <rag...@ya...> - 2011-03-25 12:36:03
|
Hi Casey, We have used Javc compiler in both the occasions (with old cobertura version and with new cobertura version), and the results are different. Is there any change that is made to new version of cobertura ? Why are the results different when compared to old version ? Satya --- On Fri, 3/18/11, Casey McGinty <cas...@gm...> wrote: From: Casey McGinty <cas...@gm...> Subject: Re: [Cobertura-devel] Issue with latest cobertura code coverage metrics To: "Satyanarayana" <rag...@ya...> Cc: cob...@li... Date: Friday, March 18, 2011, 12:54 AM I noticed a similar problem. It was not related to change in Cobertura though so maybe your issue is different. I determined that using Eclipse vs Javc compiler would give different results. When compiling with eclipse, multiline code would be counted as more than one statement. So you may want to check that. I would make sure you compile with javac and retest your result. - Casey 2011/3/16 Satyanarayana <rag...@ya...> Hi, We are finding that the code coverage metrics reported by previous version and new version of cobertura (1.9.4.1) are inconsistent. When we ran automation regression suite using previous version of cobertura we observed that the total code coverage % was reported as 31%. Later when we took latest version of cobertura ((1.9.4.1) and when we ran the same automation regression suite as above, we are seeing that the total code coverage % metrics are reported as 11% Regards, Satya ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Cobertura-devel mailing list Cob...@li... https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
|
From: Fabien B. <fba...@gm...> - 2011-03-22 11:35:18
|
Hi, I notice today that Cobertura is making use of Apache Jakarta ORO that is no more maintained. Is there a plan to move to another tool ? Cheers, Fabien |
|
From: fabien b. <fab...@al...> - 2011-03-22 10:55:29
|
Hi, I notice today that Cobertura is making use of Apache Jakarta ORO that is no more maintained. Is there a plan to move to another tool ? Cheers, Fabien |
|
From: Casey M. <cas...@gm...> - 2011-03-17 19:24:40
|
I noticed a similar problem. It was not related to change in Cobertura though so maybe your issue is different. I determined that using Eclipse vs Javc compiler would give different results. When compiling with eclipse, multiline code would be counted as more than one statement. So you may want to check that. I would make sure you compile with javac and retest your result. - Casey 2011/3/16 Satyanarayana <rag...@ya...> > Hi, > > > We are finding that the code coverage metrics reported by previous version > and new version of cobertura (1.9.4.1) are inconsistent. > > > When we ran automation regression suite using previous version of cobertura > we observed that the total code coverage % was reported as 31%. > > > > Later when we took latest version of cobertura ((1.9.4.1) and when we ran > the same automation regression suite as above, we are seeing that the total > code coverage % metrics are reported as 11% > > Regards, > *Satya* > > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > > |
|
From: Satyanarayana <rag...@ya...> - 2011-03-17 09:41:28
|
Hi,
We are finding that the code coverage metrics reported by previous version and new version of cobertura (1.9.4.1) are inconsistent.
When we ran automation regression suite using previous version of cobertura we observed that the total code coverage % was reported as 31%.
Later when we took latest version of cobertura ((1.9.4.1) and when we ran the same automation regression suite as above, we are seeing that the total code coverage % metrics are reported as 11%
Certain examples of discrepencies observed (The same automation regression suite was run with old and new verions of cobertura)
Package
# Classes
Line Coverage
Branch Coverage
Complexity
Old version of cobertura
Suite
9
63%
440/695
0%
0/319
4.142857142857143;4.143
com.gxs.catalog.foundation
73
66%
4346/6550
0%
0/2870
1.5161.5156695156695157;1.516
com.gxs.pim.content.util
2
36%
94/263
0%
0/44
0.0;0
com.gxs.pim.contenttype
52
55%
2144/3873
0%
0/1867
2.1772151898734178;2.177
com.haht.escenario.common.template.domain
5
76%
65/85
0%
0/34
1.767
__________________________________________________________________________________________________________________
New version of cobertura
Suite
9
0%
0/695
0%
0/319
4.533333333333333;4.533
com.gxs.catalog.foundation
73
43%
2841/6592
35%
1026/2920
2.4392.438768369489153;2.439
com.gxs.pim.content.util
2
0%
0/263
0%
0/44
1.6291.6285714285714286;1.629
com.gxs.pim.contenttype
52
0%
0/3873
0%
0/1870
3.613.6104868913857677;3.61
com.haht.escenario.common.template.domain
5
36%
31/85
2%
1/34
1.867
Not sure why the report generated using new verison of cobertura is not consistent with old version of cobertura and why there is a drastic changein the total % of code coverage from 31 % to 11% ?
Regards,
Satya
|
|
From: John W. L. <Joh...@sa...> - 2011-03-15 18:02:21
|
The format of the ser file will change shortly, and it may change at any time, so I would not inspect it. Instead, I would have <cobertura-report> generate an XML file. Get your information from it. The only way to find the lines covered in a given unit test is to run each test and generate a separate XML file for each test run. I don't know of a tool that does what you are talking about. John From: Bob Paige [mailto:bob...@gm...] Sent: Tuesday, March 15, 2011 1:15 PM To: cob...@li... Subject: [Cobertura-devel] relating recent CVS changes to code coverage What is the format of the cobertura.ser file? Is there some way I could relate the lines covered in a given unit test run to changes recently checked-in to CVS? I imagine having the .ser file data and a recent .diff file from CVS I could make the correlation myself, but if there is already a tool out there, all the better. -- Bobman |
|
From: Bob P. <bob...@gm...> - 2011-03-15 17:15:18
|
What is the format of the cobertura.ser file? Is there some way I could relate the lines covered in a given unit test run to changes recently checked-in to CVS? I imagine having the .ser file data and a recent .diff file from CVS I could make the correlation myself, but if there is already a tool out there, all the better. -- Bobman |
|
From: neeraj k. <nee...@gm...> - 2011-03-07 11:10:36
|
Hi Everyone, I started using cobertura a few hours back and I am not very good with maven either. I have the following directory structure module | |-apps | |-alert | | |-src | | |-target | | |-pom.xml | |------------------- | |-company | | |-src | | |-target | | |-pom.xml |----------------------- |-jobs | |-job1 | | |-src | | |-target | | |-pom.xml | |-job2 | | |-src | | |-target | | |-pom.xml Now, I want cobertura to exclude all the folders under modules/app but process all folders under modules/jobs , during both the instrumentation and report generation phase. Is that possible , and if yes how do I go about the config in modules/pom.xml Note : The maven cobertura:cobertura command is being run from -modules- directory. Thanks -- Neeraj |
|
From: Casey M. <cas...@gm...> - 2011-02-18 03:50:32
|
Hi, When I compile my project through eclipse (auto build), Cobertura reports every line in multi-line statements in the totals. This causes the line stats to be much higher than they should be If I clean, and use our ant-build compile step, multi-line statements are counted correctly as one line. How can I configure Eclipse not to over count multi-line statements? Regards, Casey McGinty |
|
From: Mark D. <ma...@ki...> - 2011-02-15 21:54:56
|
Hi! I got this email but I haven't used or contributed to Cobertura in years (sorry!). It sounds like a cool opportunity, though, if we're interested. I'm gonna try to remove myself as an admin from the Cobertura project on sourceforge now. --Mark ---------- Forwarded message ---------- From: Yegor Bugayenko <he...@fa...> Date: Tue, Feb 15, 2011 at 2:45 AM Subject: continuous integration for Cobertura To: the...@us... Hi Mark, I'm an active user of Cobertura and would like to thank you (and your team) for this great product. On the home page of Cobertura I see that there is no Continuous Integration solution yet (at least I didn't find any info about it). Take a look at our free hosted CI platform: www.fazend.com. I would be more than happy to setup an account there for Cobertura and configure everything myself. What do you think? — Yegor Bugayenko FaZend.com, Free Hosted Continuous Integration Platform |
|
From: Martin G. <mar...@or...> - 2011-02-12 07:30:21
|
Hi, I recently tried cobertura 1.9.4.1 on my project, found it pretty easy to use. However, in the report, I only see the line coverage numbers. Branch coverage / complexity values are all 0. What could be the cause of that? Is there any hidden switch or something else I'm not aware of? Thanks for any info/hints in advance, Martin Grebac -- Martin Grebac GlassFish/Metro/JAXB/Tooling at Oracle http://blogs.sun.com/mgrebac ICQ: 93478885 |
|
From: John W. L. <Joh...@sa...> - 2011-02-11 11:59:15
|
You definitely need 1.9.4.1 for JBoss/Tomcat. From: gopala krishna [mailto:gkn...@gm...] Sent: Friday, February 11, 2011 12:05 AM To: John W. Lewis Cc: cob...@li...; cob...@li... Subject: Re: [Cobertura-devel] cobertura.ser not created with jboss4.2.3 1.9.4 On Thu, Feb 10, 2011 at 5:20 PM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote: What version of Cobertura are you using? From: gopala krishna [mailto:gkn...@gm...<mailto:gkn...@gm...>] Sent: Thursday, February 10, 2011 4:50 AM To: cob...@li...<mailto:cob...@li...>; cob...@li...<mailto:cob...@li...> Subject: [Cobertura-devel] cobertura.ser not created with jboss4.2.3 Hi, earlier I used to get cobertura.ser file from jboss. Now with jboss4.2.3 I am not getting cobertura.ser file after server shutdown. Can anybody help me out to how can I get the coverage file. Thanks |
|
From: gopala k. <gkn...@gm...> - 2011-02-11 05:04:59
|
1.9.4 On Thu, Feb 10, 2011 at 5:20 PM, John W. Lewis <Joh...@sa...> wrote: > > > What version of Cobertura are you using? > > > > *From:* gopala krishna [mailto:gkn...@gm...] > *Sent:* Thursday, February 10, 2011 4:50 AM > *To:* cob...@li...; > cob...@li... > *Subject:* [Cobertura-devel] cobertura.ser not created with jboss4.2.3 > > > > Hi, > > earlier I used to get cobertura.ser file from jboss. Now with jboss4.2.3 I > am not getting cobertura.ser file after server shutdown. > > Can anybody help me out to how can I get the coverage file. > > > > Thanks > |
|
From: John W. L. <Joh...@sa...> - 2011-02-10 11:50:35
|
What version of Cobertura are you using? From: gopala krishna [mailto:gkn...@gm...] Sent: Thursday, February 10, 2011 4:50 AM To: cob...@li...; cob...@li... Subject: [Cobertura-devel] cobertura.ser not created with jboss4.2.3 Hi, earlier I used to get cobertura.ser file from jboss. Now with jboss4.2.3 I am not getting cobertura.ser file after server shutdown. Can anybody help me out to how can I get the coverage file. Thanks |
|
From: gopala k. <gkn...@gm...> - 2011-02-10 09:49:59
|
Hi, earlier I used to get cobertura.ser file from jboss. Now with jboss4.2.3 I am not getting cobertura.ser file after server shutdown. Can anybody help me out to how can I get the coverage file. Thanks |
|
From: gopala k. <gkn...@gm...> - 2011-02-10 07:49:50
|
Hi, As the .ser is not getting created, I even tried to call "saveGlobalProjectData" of "net.sourceforge.cobertura.coveragedata.ProjectData" in ServletContextListener. Then I noticed exception jvm 1 | 2011-02-10 12:56:30,050 INFO [STDOUT] Caused by: java.lang.NullPointerException jvm 1 | 2011-02-10 12:56:30,050 INFO [STDOUT] at net.sourceforge.cobertura.coveragedata.TouchCollector.applyTouchesOnProjectData(TouchCollec tor.java:188) jvm 1 | 2011-02-10 12:56:30,050 INFO [STDOUT] at net.sourceforge.cobertura.coveragedata.ProjectData.saveGlobalProjectData(ProjectData.java:2 67) jvm 1 | 2011-02-10 12:56:30,066 INFO [STDOUT] at net.sourceforge.cobertura.coveragedata.ProjectData.initialize(ProjectData.java:240) jvm 1 | 2011-02-10 12:56:30,066 INFO [STDOUT] at net.sourceforge.cobertura.coveragedata.TouchCollector.<clinit>(TouchCollector.java:40) How to resolve this problem. Any help is much more apprecited. Thanks |
|
From: John W. L. <Joh...@sa...> - 2011-02-01 15:54:09
|
I hope the next release will happen no later than a month from now. Piotr's branch will very likely be merged into the trunk, so I would use his branch for any internal version you may create. His branch has been deployed on several of the test servers I maintain, and it is holding up very well. It is also noticeably faster. If there is enough interest, I can do a quick release of the trunk if a month is too long to wait. I'm not sure that would help you though since you will want to use the trunk after the merge. John -----Original Message----- From: Ximon Eighteen [mailto:xim...@gm...] Sent: Saturday, January 29, 2011 6:14 AM To: cob...@li... Subject: [Cobertura-devel] Cobertura 2.0/ignore trivial release date? Good morning all, This is my first post to the list and so I have had a brief look through the list archives (as far back as June last year) for mail subjects which might relate to a new release of Cobertura but I have not found anything. My apologies if my question is already answered or this is not the correct place to ask it. I can see that the project is active, at least there are recent commits to the source repository, but I cannot find any information on when a new release of Cobertura might be expected. Specifically I want to use the accepted ignore trivla patch (http://sourceforge.net/tracker/?func=detail&aid=3010530&group_id=130558&atid=720017). I have made my own local version of Cobertura and am considering deploying it to our company internal Nexus instance but with my companies groupId instead of net.sourceforge.cobertura (to avoid confusion as mine would not be an official release). I would also deploy a slightly modified version of the maven cobertura plugin which depends on my modified cobertura and passes through the ignore trivial command line flag, again with my own groupId. I thought I should ask here before proceeding in case a release including this feature is imminent or if you advise that I proceed differently. Any feedback would be greatly appreciated. Ximon ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Cobertura-devel mailing list Cob...@li... https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
|
From: Ximon E. <xim...@gm...> - 2011-01-29 11:14:26
|
Good morning all, This is my first post to the list and so I have had a brief look through the list archives (as far back as June last year) for mail subjects which might relate to a new release of Cobertura but I have not found anything. My apologies if my question is already answered or this is not the correct place to ask it. I can see that the project is active, at least there are recent commits to the source repository, but I cannot find any information on when a new release of Cobertura might be expected. Specifically I want to use the accepted ignore trivla patch (http://sourceforge.net/tracker/?func=detail&aid=3010530&group_id=130558&atid=720017). I have made my own local version of Cobertura and am considering deploying it to our company internal Nexus instance but with my companies groupId instead of net.sourceforge.cobertura (to avoid confusion as mine would not be an official release). I would also deploy a slightly modified version of the maven cobertura plugin which depends on my modified cobertura and passes through the ignore trivial command line flag, again with my own groupId. I thought I should ask here before proceeding in case a release including this feature is imminent or if you advise that I proceed differently. Any feedback would be greatly appreciated. Ximon |
|
From: John W. L. <Joh...@sa...> - 2011-01-24 23:42:28
|
Cobertura is not consistent with how it is doing conditional coverage for switch statements. Piotr's branch handles them much better, but I want to go over it so there are no surprises with the next release.
First of all, there are two ways to look at the coverage of a switch statement. Consider the following statement:
switch (e) {
case FOO:
case BAR:
case GONK:
return true;
default:
return false;
}
One way of thinking of this is that you have 4 different cases that you may want to cover in your tests. If your tests only set 'e' to GONK, then the coverage would be 1/4. The other way of thinking of this is that there are 2 different code blocks. If your tests only set 'e' to GONK, then the coverage would be 1/2 since the first block (return true) was covered.
Since Cobertura does not look at the source, we are at the mercy of how the compiler handles switch statements. Generally, if you have gaps in your cases, the compiler puts extra cases in your class files. Consider the following switch statement that contains gaps:
switch (i) {
case 15:
System.out.println("15");
break;
case 16:
System.out.println("16");
break;
case 17:
System.out.println("17");
break;
case 18:
System.out.println("18");
break;
// intentionally skip 19 and 20
case 21:
System.out.println("21");
break;
default:
System.out.println("default");
}
The compiler will interpret this as if you had written the following (note that case 19 and 20 are with the default):
switch (i) {
case 15:
System.out.println("15");
break;
case 16:
System.out.println("16");
break;
case 17:
System.out.println("17");
break;
case 18:
System.out.println("18");
break;
case 21:
System.out.println("21");
break;
case 19:
case 20:
default:
System.out.println("default");
}
So, because Cobertura only looks at the classes, we can only keep track of the coverage of the blocks - not the cases. Currently, Cobertura does not do a good job of this. This bug has a good example of the problem:
http://sourceforge.net/tracker/?func=detail&aid=2998305&group_id=130558&atid=720015
Next, I want to show a few examples and show how Piotr's branch is handling them.
Back to the first example presented above:
switch (e) {
case FOO:
case BAR:
case GONK:
return true;
default:
return false;
}
If FOO, BAR, and GONK are all covered, but the default is not, then the coverage will be reported as 1/2. This is because the compiler combines FOO, BAR, and GONK into the same code block.
Similarly, if FOO is the only thing covered, the coverage will be reported as 1/2.
Next example:
switch (i) {
case 1:
System.out.println("1");
break;
case 2:
System.out.println("2");
break;
}
Assuming i==2 is covered, the coverage is 1/3. The third is the default.
Next example:
switch (i) {
case 2:
System.out.println("2");
break;
case 3:
System.out.println("3");
break;
case 1:
default:
System.out.println("1 or default");
}
Assuming i==5 and i==1 are covered, the coverage will be reported as 1/3. Since case 1 falls through to the default, it is considered as a single condition of the switch statement. The compiler considers it such.
Next example:
switch (e) {
case FOO:
System.out.println("FOO");
case BAR:
System.out.println("BAR");
return true;
case GONK:
return true;
default:
return false;
}
Note that FOO falls through to BAR. If FOO is the only thing covered, the coverage will be 1/4. BAR is not considered covered although execution fell through to it. (the line coverage will show BAR to be covered, but the conditional coverage will not.)
If FOO and BAR are exercised during testing, then the coverage will be 2/4.
Note that this is a little confusing because if FOO and BAR shared a block like this:
switch (e) {
case FOO:
case BAR:
System.out.println("FOO or BAR");
return true;
case GONK:
return true;
default:
return false;
}
Then, if FOO and BAR are covered, the coverage is reported as 1/3 because FOO and BAR share the same block.
Generally speaking, a case is not considered a case of its own unless it has a block of its own. Also, if multiple cases share the same block they are combined as one case.
This method seems to be reporting coverage in a much less confusing way overall.
John
|
|
From: John W. L. <Joh...@sa...> - 2011-01-21 21:43:31
|
It may be that you are just experimenting, but typically, you use the cobertura.ser file that is produced during instrumentation. I would not expect it to get bigger. I know of a test project that has a cobertura.ser file that is 4.75MB. So, I would not expect 2MB to be a problem. Piotr's branch will very likely be merged into the trunk, so I would not hesitate to try it. John From: Steven Christou [mailto:ste...@re...] Sent: Friday, January 21, 2011 4:13 PM To: Piotr Tabor Cc: John W. Lewis; cob...@li... Subject: Re: [Cobertura-devel] Cobertura Limits I am currently using trunk, I have yet to try your changes. The failure is occurring during 'business', I also notice it is doing flushes correctly, and it's producing results. The cobertura.ser file gets to about 2mb before the crash occurs. I am flushing after every test with the assumption garbage collection will clean up everything, and garbage collection will shrink the array size. I want to refrain from doing explicit GC calls unless absolutely necessary. On 1/21/2011 2:49 PM, Piotr Tabor wrote: Steven, Do you have problems with both branches, or only with trunk. AFAIK the running size of instrumented code in my branch does not grow in time ? Are your code going out of memory during 'business' run or during flush ? Piotr On Fri, Jan 21, 2011 at 5:29 PM, Steven Christou <ste...@re...<mailto:ste...@re...>> wrote: We changed our code recently to include the ability to flush cobertura data in our JVM at any point using the suggested code in the FAQ page. Is this going to help remove this memory limit? We set our heap space to -Xmx1400m which I believe is really high, and it did not solve the issue with memory. On 1/11/2011 5:07 PM, John W. Lewis wrote: > There is a memory limit. All of the line and conditional counts are kept in memory till the JVM is shut down and they are flushed to disk. > > So, as more instrumented code is executed in the test process, the more memory is used by the test process. > > Then, when the shutdown occurs, the cobertura.ser file is loaded into memory, and the in-memory counts are merged before being written to the disk again. > > John > > > -----Original Message----- > From: Steven Christou [mailto:ste...@re...<mailto:ste...@re...>] > Sent: Tuesday, January 11, 2011 5:48 PM > To: 'cob...@li...<mailto:cob...@li...>' > Subject: [Cobertura-devel] Cobertura Limits > > I was wondering if cobertura had any kind of limits. I ran into an issue where I believe something was happening and the server was starting to crash. The JVM never shut down, but at the same time, when running fitnesse tests, I was getting nothing but failures. I could run all my tests uninstrumented, and they would all pass. This happens after I run several hundred tests though, so I'm assuming I must be hitting a limit. > > I tried running with Piotr's changes, but I am running into an issue where the tests do not even run. > Email Disclaimer: > http://www.redprairie.com/emaildisclaimer/ > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Cobertura-devel mailing list > Cob...@li...<mailto:Cob...@li...> > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > > Email Disclaimer: http://www.redprairie.com/emaildisclaimer/ ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Cobertura-devel mailing list Cob...@li...<mailto:Cob...@li...> https://lists.sourceforge.net/lists/listinfo/cobertura-devel -- Pozdrawiam, Piotr Tabor Email Disclaimer: http://www.redprairie.com/emaildisclaimer/ |
89 messages has been excluded from this view by a project administrator.
