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: KARR, D. <dk...@at...> - 2012-08-27 20:55:18
|
> -----Original Message----- > From: Daniel Zapata [mailto:dz...@gm...] > Sent: Monday, August 27, 2012 11:23 AM > To: KARR, DAVID > Cc: cob...@li... > Subject: Re: [Cobertura-devel] Where is a doc that explains details of > the cobertura report? > > I have not found such a doc, but I did spend some time studying them. > Anyone else, please correct me if I am wrong. > > Basically, any line with a color is eligible for coverage. That > second column tells you how many times a line was executed. A line is > completely green (all columns, from the line number to the code) if > that line is fully covered. This means all the conditions of that > line have been executed (like an if condition). If the line number is > green but the execution count+code is red, that line has not been > fully executed. > > When I look at the class coverage report, I look for zeroes in the > second column to see where I should focus my coverage. > > Hope that helps, > Danny Yup, that helps. It seemed pretty likely that's what the value indicated, but as I found nothing anywhere that stated this, I wanted to confirm that. I suppose I could dig into the source code, but you would think someone would have written this down somewhere. > On Fri, Aug 24, 2012 at 4:01 PM, KARR, DAVID <dk...@at...> wrote: > > I've seen several pages that show how to generate the cobertura > coverage report, but it seems hard to find something that specifies > exactly what it generates and what all of the values mean. > > > > The vast majority of it is pretty obvious, but there's one thing that > is not completely obvious. When viewing the coverage within each file, > the first column shows line numbers. The second column is either blank > or a number. I'm guessing this number is something like an occurrence > count, but there aren't any labels on the display, and I can't find any > documentation that says exactly what this value represents. > > > > --------------------------------------------------------------------- > --------- > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. > Discussions > > will include endpoint security, mobile security and the latest in > malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Cobertura-devel mailing list > > Cob...@li... > > https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
|
From: Daniel Z. <dz...@gm...> - 2012-08-27 18:23:52
|
I have not found such a doc, but I did spend some time studying them. Anyone else, please correct me if I am wrong. Basically, any line with a color is eligible for coverage. That second column tells you how many times a line was executed. A line is completely green (all columns, from the line number to the code) if that line is fully covered. This means all the conditions of that line have been executed (like an if condition). If the line number is green but the execution count+code is red, that line has not been fully executed. When I look at the class coverage report, I look for zeroes in the second column to see where I should focus my coverage. Hope that helps, Danny On Fri, Aug 24, 2012 at 4:01 PM, KARR, DAVID <dk...@at...> wrote: > I've seen several pages that show how to generate the cobertura coverage report, but it seems hard to find something that specifies exactly what it generates and what all of the values mean. > > The vast majority of it is pretty obvious, but there's one thing that is not completely obvious. When viewing the coverage within each file, the first column shows line numbers. The second column is either blank or a number. I'm guessing this number is something like an occurrence count, but there aren't any labels on the display, and I can't find any documentation that says exactly what this value represents. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
|
From: KARR, D. <dk...@at...> - 2012-08-24 23:02:10
|
I've seen several pages that show how to generate the cobertura coverage report, but it seems hard to find something that specifies exactly what it generates and what all of the values mean. The vast majority of it is pretty obvious, but there's one thing that is not completely obvious. When viewing the coverage within each file, the first column shows line numbers. The second column is either blank or a number. I'm guessing this number is something like an occurrence count, but there aren't any labels on the display, and I can't find any documentation that says exactly what this value represents. |
|
From: Zschocke, F. <Flo...@cy...> - 2012-08-23 06:56:20
|
What makes you think that Cobertura is at fault here?
From what I see the errors are caused by the axis2-wsdl2code:wsdl2code execution and then by the Squid AST scan. The Cobertura instrumentation and report generation apparently run successfully.
But since you do not run any tests anyhow, you don’t need the Cobertura run either. So you may want to upgrade Sonar to 3.2. That version a) defaults to JaCoCo for coverage and b) doesn’t run the coverage by default anymore (my experience, YMMV).
From: Gaspar Almazan [mailto:gal...@tc...]
Sent: Wednesday, August 22, 2012 5:54 PM
To: cob...@li...
Subject: [Cobertura-devel] org.sonar.squid.api.AnalysisException: The source directory does not correspond to the package declaration
Hi.
We are having problems in two completly different projects with our new Sonar 3.0 installation (NOT happening with our older Sonar 2.4):
Goal: clean verify -Dmaven.test.skip sonar:sonar
Maven: /software/apache-maven-2.2.1
JDK: /usr/java/jdk1.5.0_22
Options: -Xmx2048m -XX:MaxPermSize=1024m
In the maven log we can see this first error (but the analysis continues):
[16:20:10]: [INFO] ------------------------------------------------------------------------
[16:20:10]: [INFO] Building MetacontenidosSrv
[16:20:10]: [INFO] task-segment: [org.codehaus.mojo:cobertura-maven-plugin:2.5.1:cobertura]
[16:20:10]: [INFO] ------------------------------------------------------------------------
[16:20:10]: [INFO] Preparing cobertura:cobertura
[16:20:10]: [INFO] [axis2-wsdl2code:wsdl2code {execution: Metacontenidos Services}]
[16:20:10]: Retrieving document at '/apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/src/main/resources/axis2/MetacontenidosSrv-5.0..wsdl'.
[16:20:10]: Retrieving schema at 'metacontenido.xsd', relative to 'file:/apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/src/main/resources/axis2/MetacontenidosSrv-5.0.wsdl'.
[16:20:10]: Retrieving schema at 'Exception.xsd', relative to 'file:/apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/src/main/resources/axis2/MetacontenidosSrv-5.0.wsdl'.
[16:20:12]: 21-ago-2012 16:20:11 org.apache.axis2.util.XMLPrettyPrinter$1 fatalError
[16:20:12]: GRAVE: Exception occurred while trying to pretty print file /apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/target/main/axis2/services.xml
[16:20:12]: ; Line#: -1; Column#: -1
[16:20:12]: javax.xml.transform.TransformerException: Premature end of file.
[16:20:12]: at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:780)
[16:20:12]: at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:756)
Finally this errors aborts Sonar analysis:
[16:20:20]: -------------------------------------------------------
[16:20:20]: T E S T S
[16:20:20]: -------------------------------------------------------
[16:20:20]: There are no tests to run.
[16:20:20]: Results :
[16:20:20]: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[16:20:20]: [INFO] [cobertura:cobertura {execution: default-cli}]
[16:20:22]: [INFO] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[16:20:22]: Cobertura: Loaded information on 6 classes.
[16:20:22]: Report time: 1087ms
[16:20:22]: [INFO] Cobertura Report generation was successful.
[16:20:22]: [INFO] [16:20:22.075] Execute org.codehaus.mojo:cobertura-maven-plugin:2.5.1:cobertura done: 11707 ms
[16:20:22]: [INFO] [16:20:22.075] Execute maven plugin cobertura-maven-plugin done: 11707 ms
[16:20:22]: [INFO] [16:20:22.076] Initializer CoberturaMavenInitializer...
[16:20:22]: [INFO] [16:20:22.076] Initializer CoberturaMavenInitializer done: 0 ms
[16:20:22]: [INFO] [16:20:22.144] Sensor JavaSourceImporter...
[16:20:22]: [INFO] [16:20:22.936] Sensor JavaSourceImporter done: 792 ms
[16:20:22]: [INFO] [16:20:22.936] Sensor SquidSensor...
[16:20:22]: [INFO] [16:20:22.954] Java AST scan...
[16:20:23]: [ERROR] [16:20:23.053] Squid Error occurs when analysing :/apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/src/main/java/es/yell/services/wsmetacontenidos/contract/server/ServiceClass.java
[16:20:23]: org.sonar.squid.api.AnalysisException: The source directory does not correspond to the package declaration es.yell.services.wsmetacontenidos.contract.server
[16:20:23]: at org.sonar.java.ast.visitor.PackageVisitor.checkPhysicalDirectory(PackageVisitor.java:93) ~[sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.java.ast.visitor.PackageVisitor.createSourcePackage(PackageVisitor.java:75) ~[sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.java.ast.visitor.PackageVisitor.visitFile(PackageVisitor.java:50) ~[sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.java.ast.CheckstyleSquidBridge.beginTree(CheckstyleSquidBridge.java:61) ~[sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at com.puppycrawl.tools..checkstyle.TreeWalker.notifyBegin(TreeWalker.java:351) [checkstyle-5.5.jar:5.5]
[16:20:23]: at com.puppycrawl.tools..checkstyle.TreeWalker.walk(TreeWalker.java:326) [checkstyle-5.5.jar:5.5]
[16:20:23]: at com.puppycrawl.tools..checkstyle.TreeWalker.processFiltered(TreeWalker.java:188) [checkstyle-5.5..jar:5.5]
[16:20:23]: at com.puppycrawl.tools..checkstyle.api.AbstractFileSetCheck.process(AbstractFileSetCheck.java:73) [checkstyle-5.5.jar:5.5]
[16:20:23]: at com.puppycrawl.tools..checkstyle.Checker.process(Checker.java:262) [checkstyle-5.5.jar:5.5]
[16:20:23]: at org.sonar.java.ast.JavaAstScanner.launchCheckstyle(JavaAstScanner.java:117) [sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.java.ast.JavaAstScanner.scanFiles(JavaAstScanner.java:102) [sonar-squid-java-plugin-3..0.jar:na]
[16:20:23]: at org.sonar.plugins.squid.SquidExecutor.scanSources(SquidExecutor.java:170) [sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.plugins.squid.SquidExecutor.scan(SquidExecutor.java:85) [sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.plugins.squid.SquidSensor.analyzeMainSources(SquidSensor.java:82) [sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.plugins.squid.SquidSensor.analyse(SquidSensor.java:65) [sonar-squid-java-plugin-3.0.jar:na]
[16:20:23]: at org.sonar.batch.phases.SensorsExecutor.execute(SensorsExecutor.java:64) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.phases.Phases.execute(Phases.java:93) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.ProjectModule.doStart(ProjectModule.java:143) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.Module.start(Module.java:83) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.BatchModule.analyze(BatchModule.java:115) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.BatchModule.analyze(BatchModule.java:110) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.BatchModule.doStart(BatchModule.java:105) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.Module.start(Module.java:83) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.BootstrapModule.doStart(BootstrapModule.java:109) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrap.Module.start(Module.java:83) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrapper.Batch.startBatch(Batch.java:72) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:59) [sonar-batch-3.0.jar:na]
[16:20:23]: at org.sonar.maven.SonarMojo.execute(SonarMojo.java:151) [sonar-maven-plugin-3.0.jar:na]
[16:20:23]: at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:98) [sonar-maven-plugin-1.0-beta-2.jar:na]
[16:20:23]: at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:79) [sonar-maven-plugin-1.0-beta-2.jar:na]
[16:20:23]: at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:88) [sonar-maven-plugin-1.0-beta-2.jar:na]
[16:20:23]: at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.cli..MavenCli.main(MavenCli.java:362) [maven-2.2.1-uber.jar:2.2.1]
[16:20:23]: at org.apache.maven.cli..compat.CompatibleMain.main(CompatibleMain.java:60) [maven-2.2.1-uber.jar:2..2.1]
[16:20:23]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_18]
[16:20:23]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_18]
[16:20:23]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_18]
[16:20:23]: at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_18]
[16:20:23]: at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [classworlds-1.1.jar:1.1]
[16:20:23]: at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [classworlds-1.1.jar:1.1]
[16:20:23]: at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [classworlds-1.1.jar:1.1]
[16:20:23]: at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [classworlds-1.1.jar:1.1]
[16:20:23]: [INFO] ------------------------------------------------------------------------
[16:20:23]: [ERROR] BUILD ERROR
[16:20:23]: [INFO] ------------------------------------------------------------------------
[16:20:23]: [INFO] Can not execute Sonar
[16:20:23]: Embedded error: Ocurrió una excepción - org.sonar.squid.api.AnalysisException: The source directory does not correspond to the package declaration es.yell.services.wsmetacontenidos.contract.server, file : /apps/yell01_teamcity/buildAgent2/work/8c49ad815ef554e2/branches/5.0.643/trunk/meta5Parent/metaSrv/src/main/java/es/yell/services/wsmetacontenidos/contract/server/ServiceClass.java, line : 0
[16:20:23]: [INFO] ------------------------------------------------------------------------
[16:20:23]: [INFO] For more information, run Maven with the -e switch
[16:20:23]: [INFO] ------------------------------------------------------------------------
[16:20:23]: [INFO] Total time: 4 minutes 16 seconds
[16:20:23]: [INFO] Finished at: Tue Aug 21 16:20:23 CEST 2012
[16:20:24]: [INFO] Final Memory: 97M/316M
[16:20:24]: [INFO] ------------------------------------------------------------------------
[16:20:24]: Number of processed tests: 18
[16:20:24]: Publishing artifacts (1s)
These are the cobertura jars (we think cobertura is the "problem"):
/home/tcadmin/.m2/repository/net/sourceforge/cobertura
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura/1.9.4.1<http://1.9.4.1>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura/1.9.4..1/cobertura-1.9.4.1.jar<http://1.9.4.1/cobertura-1.9.4.1.jar>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura/1.9.4.1/cobertura-1.9.4.1.pom<http://1.9.4.1/cobertura-1.9.4.1.pom>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura/1.9.4.1/cobertura-1.9.4.1.pom.sha1<http://1.9.4.1/cobertura-1.9.4.1.pom.sha1>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura/1.9.4.1/cobertura-1.9.4.1.jar.sha1<http://1.9.4.1/cobertura-1.9.4.1.jar.sha1>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura-runtime
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura-runtime/1.9.4.1<http://1.9.4.1>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura-runtime/1.9.4.1/cobertura-runtime-1.9.4.1.pom.sha1<http://1.9.4.1/cobertura-runtime-1.9.4.1.pom.sha1>
/home/tcadmin/.m2/repository/net/sourceforge/cobertura/cobertura-runtime/1.9.4.1/cobertura-runtime-1.9.4.1.pom<http://1.9.4.1/cobertura-runtime-1.9.4.1.pom>
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin/2.5.1
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin/2.5.1/cobertura-maven-plugin-2.5.1.pom
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin/2.5.1/cobertura-maven-plugin-2.5.1.pom.sha1
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin/2.5.1/cobertura-maven-plugin-2.5.1.jar
/home/tcadmin/.m2/repository/org/codehaus/mojo/cobertura-maven-plugin/2.5.1/cobertura-maven-plugin-2.5.1.jar.sha1
ServiceClass path: metaSrv\src\main\java\es\yell\services\wsmetacontenidos\contract\server
The steps maven takes are these:
Step 1: SVN code downloaded
Step 2: WSDL2Code (maven axis2 plugin) generates new clases
Step 3: MVN compiles step 1 and 2 code without any warning/error
Step 4: Sonar analisys is launched
Funny thing is that when we don't take step 2, everything works ok.
We are completly lost and we are considering using another Cobertura version, or downgrade to Sonar v2.4 (or upgrade to 3.2 if that could be a fix to this problem).
|
|
From: Rami V. <rv...@re...> - 2012-08-13 15:38:19
|
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ |
|
From: John W. L. <Joh...@sa...> - 2012-08-13 14:57:57
|
It is creating the same report because it is using the cobertura.ser file that was created during instrumentation. If you want an empty report, you need to do the instrumentation again specifying no classes.
By the way, the fileset used in <cobertura-report> is only used to locate the source files for the classes that are in the cobertura.ser file. When you remove the fileset, the report will have broken links when you click on the classname links.
John
From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...]
Sent: Wednesday, August 08, 2012 6:12 PM
To: John W. Lewis
Cc: cob...@li...
Subject: Coverage report results - I am having issues. Is it refering IE cache. How to clear cache to get latest report.
Hello Cobertura users.
I have below coverage task 1, to generate cobertura report.
----------------------------------------------------
<target name="Html-coverage-report">
<!-- Generate a series of HTML files containing the coverage Data in a user-readable form using nested source filesets.-->
<echo>=== HTML CODE COVERAGE REPORT ===</echo>
<cobertura-report format="html" destdir="${coverage.html.dir}" >
<fileset dir="C:/Documents and Settings/m095351/IBM/rationalsdp/workspace/QReads">
<include name="**/*.java" />
<exclude name="Unittest/*.java" />
<exclude name="Unittest/junit/*.java" />
</fileset>
</cobertura-report>
<echo>Done compiling Html-coverage-report.</echo>
</target>
-------------------------------------------------------------------------------------
The above task generated a good report, as expected.
Then i modified the same coverage task as coverage task2 to remove the fileset part as below ,want to create an empty report and run the task..
<target name="Html-coverage-report">
<!-- Generate a series of HTML files containing the coverage Data in a user-readable form using nested source filesets.-->
<echo>=== HTML CODE COVERAGE REPORT ===</echo>
<cobertura-report format="html" destdir="${coverage.html.dir}" >
</cobertura-report>
<echo>Done compiling Html-coverage-report.</echo>
</target>
The above coverage task2 should create empty report. Instead, i get report generated properly with all my packages as when i run the coverage task 1 .
I think the report refers to Internet explorer cache and brings the original report. I went to IE and clear browser history and run report. No luck. Any idea how to clear the cache and genearte updated coverage report.?
Your help is highly appreciated.
thanks
Sakthi.
|
|
From: Rami V. <rv...@re...> - 2012-08-13 13:45:20
|
On 08/09/2012 04:19 PM, *** From Sakthivel Kumar*** wrote:
> Please see my thoughts embedded in your notes in blue. Try this and
> update the group about your findings.
> thanks.
>
> On Thu, Aug 9, 2012 at 2:43 AM, Rami Vaknin <rv...@re...
> <mailto:rv...@re...>> wrote:
>
> On 08/09/2012 06:25 AM, *** From Sakthivel Kumar*** wrote:
>>
>> Hello Rami.
>> Are you testing your applicaiton using JUnit or is it automation
>> testing?
>> If so, what kind of application server you are using. External
>> server or local server?
>
> Thanks for the quick response.
>
> My application is running under jboss and I'm testing my
> application using automation test.
>
> *Sakthi:* Is this the first time you are trying with corbertura to
> create reports or everything was working good and suddenly you are
> getting issues in your LOCK file.?
First time.
> If this is the first time, then try below and see if it works.
> Are you using local Jboss server or external Jboss server for your
> covearage testing? If you are using external JBOSS server, instead, if
> possible try deploying your application EAR file that you deployed in
> external JBOss server to your local server and run your automation
> testing and see if cobertura.ser file is getting created in your local
> server working directory after your local server shut down. And see if
> LOCK is not giving problem.Some times external servers may give issue.
It's local jboss server.
I tried to workaround the permissions issue with cobertura.ser.lock (I
gave write permission to / dir) but I still get coverage of 0%.
I'm doing the instrumentation on jar files in-place: I'm stopping the
jboss server, do the instrumentation and then start the server again,
the cobertura.ser is created immediately during the instrumentation
operation (before server starts) and does not change (nor in size
neither in time stamp) when the server is going down.
I tried to run my server with and without the following arguments:
-Dnet.sourceforge.cobertura.datafile=/usr/share/jbossas/bin/cobertura.ser
-Djboss.shutdown.forceHalt=false
My ant task makes sure that the uninstrumented jars are backed-up and
the jars are instrumented in-place in their original location and
deleted when before any new instrumentation starts.
My cobertura-instrument part from the ant task is:
<cobertura-instrument datafile="${bin.dir}/cobertura.ser">
<fileset dir="${engine-ear-lib.dir}">
<include name="${1st-jar-name}" />
<include name="${2nd-jar-name}" />
<include name="${3rd-jar-name}" />
<include name="${4th-jar-name}" />
<include name="${5th-jar-name}" />
<include name="${6th-jar-name}" />
</fileset>
</cobertura-instrument>
My ant task's instrumentation output:
instrument:
...
...
[cobertura-instrument] Cobertura null - GNU GPL License (NO WARRANTY) -
See COPYRIGHT file [cobertura-instrument] Instrumenting 6 files
[cobertura-instrument] log4j:WARN No appenders could be found for logger
(net.sourceforge.cobertura.instrument.Main). [cobertura-instrument]
log4j:WARN Please initialize the log4j system properly.
[cobertura-instrument] Cobertura: Saved information on 2619 classes.
[cobertura-instrument] Instrument time: 8685ms
BUILD SUCCESSFUL
> Also the cobertura instrumentation and report is done via a script.
>
> *Sakthi:* Are you not using cobertura instrumentation task and report
> task and is there any reason you are using a script for this.? Can you
> please share the script so that i can take a look.
My automation script prepare the environment, runs the
cobertura-instrument ant task, then it runs the test itself and in the
end it runs cobertura-report and a clean task that overrides the
instrumented jars with the uninstrumented jars from the backup, and
deletes the cobertura.ser from the server's bin directory.
I already verified that my cobertura-report code works well - I took
cobertura.ser file from a colleague that works on the same project on
development environment, and I ran the cobertura-report on it, I got the
coverage report with the right coverage.
> Basically if you are not using the right cobertura.ser file created
> during instrumentation of your client/server files (Class or Jars) ,
> you may get LOCK issues.
>
> I already use the :
> "-Dnet.sourceforge.cobertura.datafile=/usr/share/jbossas/bin/cobertura.ser"
> while starting jboss server so I can't find why the creation of
> the lock file is in /cobertura.ser.lock.
>
>> Also please go to below link and read under heading
>> http://cobertura.sourceforge.net/faq.html
>>
>>
>> Usage
>>
>> When I generate coverage reports, why do they always show 100%
>> coverage everywhere?
>>
>> When I generate coverage reports, why do they always show 0%
>> coverage everywhere?
>>
>> Also read below item in the same link. You may get some pointers.
>> Hope this helps.
>> Good luck
>> Sakthi
>>
>>
>> Using Cobertura with a Web Application
>>
>> I have automated tests that use
>> HttpUnit/HtmlUnit/Empirix/Rational Robot, can I use Cobertura?
>>
>> Yes! The process is a bit more involved, but the concept is the
>> same. First instrument your compiled classes. Then create your
>> war file. Then deploy the war file into your application server
>> (Tomcat, JBoss, WebLogic, WebSphere, etc). Now run your tests.
>>
>> As your classes are accessed, they will create a "cobertura.ser"
>> file on the disk. You may need to dig around a bit to find it.
>> Cobertura puts this file in what it considers to be the current
>> working directory. Typically this is the directory that the
>> application server was started from (for example,
>> |C:\Tomcat\bin|) Note: *This file is not written to the disk
>> until the application server exits*. See below for how to work
>> around this.
>>
>> Now that you know where the cobertura.ser file is, you should
>> modify your deploy step so that it moves the original
>> cobertura.ser to the appropriate directory in your application
>> server, and then moves it back when finished testing. Then run
>> cobertura-report.
>>
>>
>> I'm using JBoss. When I stop the server, the coverage data file
>> is not written. Or the coverage data file is 0 bytes. Or
>> cobertura-report and cobertura-merge complain that the coverage
>> data file is invalid (possibly throwing an EOFException).
>>
>> Cobertura only writes the coverage data file at shutdown. It does
>> this by adding a shutdown hook
>> with|Runtime.getRuntime().addShutdownHook()|. JBoss has its own
>> shutdown hook that calls |System.halt()|when its finished. If the
>> JBoss shutdown hook finishes before the Cobertura shutdown hook,
>> then the call to |System.halt()|causes the JVM to halt and the
>> cobertura.ser file will be incomplete.
>>
>> To fix this, set |-Djboss.shutdown.forceHalt=false|when starting
>> JBoss.
>>
>>
>>
>> On Wed, Aug 8, 2012 at 6:32 PM, Rami Vaknin <rv...@re...
>> <mailto:rv...@re...>> wrote:
>>
>> Hi,
>>
>> I'm trying to use cobertura using ant task, I get only 0%
>> coverage due
>> to the following error which occurs when shuting down jvm for
>> cobertura
>> to flush changes into cobertura.ser:
>>
>> 01:32:24,187 ERROR [stderr] Unable to get lock channel for
>> /cobertura.ser.lock: cobertura.ser.lock (Permission denied)
>>
>> Could you please explain:
>>
>> 1. Why the lock file is created on / while the cobertura.ser
>> is in
>> /usr/share/blahblah (misconfiguration?), what defines the
>> lock file location
>> 2. Which process/component is trying to create that lock file?
>>
>> Note that I found 2 old email threads regarding this issue but I
>> couldn't understand how to solve that from the threads solutions.
>>
>> --
>>
>> Thanks,
>>
>> Rami Vaknin, QE @ Red Hat, TLV, IL.
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
>> Discussions
>> will include endpoint security, mobile security and the
>> latest in malware
>> threats.
>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Cobertura-devel mailing list
>> Cob...@li...
>> <mailto:Cob...@li...>
>> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>>
>>
>>
>>
>> --
>> Thanks and Best Regards
>>
>> Sakthivel Kumar
>>
>> nsa...@gm... <mailto:nsa...@gm...>
>
>
> --
>
> Thanks,
>
> Rami Vaknin, QE @ Red Hat, TLV, IL.
>
>
>
>
> --
> Thanks and Best Regards
>
> Sakthivel Kumar
>
> nsa...@gm... <mailto:nsa...@gm...>
--
Thanks,
Rami Vaknin, QE @ Red Hat, TLV, IL.
|
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-09 13:19:48
|
Please see my thoughts embedded in your notes in blue. Try this and update the group about your findings. thanks. On Thu, Aug 9, 2012 at 2:43 AM, Rami Vaknin <rv...@re...> wrote: > On 08/09/2012 06:25 AM, *** From Sakthivel Kumar*** wrote: > > > Hello Rami. > > Are you testing your applicaiton using JUnit or is it automation testing? > If so, what kind of application server you are using. External server or > local server? > > > Thanks for the quick response. > > My application is running under jboss and I'm testing my application using > automation test. > *Sakthi:* Is this the first time you are trying with corbertura to create reports or everything was working good and suddenly you are getting issues in your LOCK file.? If this is the first time, then try below and see if it works. Are you using local Jboss server or external Jboss server for your covearage testing? If you are using external JBOSS server, instead, if possible try deploying your application EAR file that you deployed in external JBOss server to your local server and run your automation testing and see if cobertura.ser file is getting created in your local server working directory after your local server shut down. And see if LOCK is not giving problem.Some times external servers may give issue. > Also the cobertura instrumentation and report is done via a script. > *Sakthi:* Are you not using cobertura instrumentation task and report task and is there any reason you are using a script for this.? Can you please share the script so that i can take a look. Basically if you are not using the right cobertura.ser file created during instrumentation of your client/server files (Class or Jars) , you may get LOCK issues. > I already use the : > "-Dnet.sourceforge.cobertura.datafile=/usr/share/jbossas/bin/cobertura.ser" > while starting jboss server so I can't find why the creation of the lock > file is in /cobertura.ser.lock. > > > Also please go to below link and read under heading > http://cobertura.sourceforge.net/faq.html > Usage > > When I generate coverage reports, why do they always show 100% coverage > everywhere? > > When I generate coverage reports, why do they always show 0% coverage > everywhere? > > Also read below item in the same link. You may get some pointers. > > Hope this helps. > > Good luck > Sakthi > > Using Cobertura with a Web Application > > I have automated tests that use HttpUnit/HtmlUnit/Empirix/Rational Robot, > can I use Cobertura? > > Yes! The process is a bit more involved, but the concept is the same. > First instrument your compiled classes. Then create your war file. Then > deploy the war file into your application server (Tomcat, JBoss, WebLogic, > WebSphere, etc). Now run your tests. > > As your classes are accessed, they will create a "cobertura.ser" file on > the disk. You may need to dig around a bit to find it. Cobertura puts this > file in what it considers to be the current working directory. Typically > this is the directory that the application server was started from (for > example, C:\Tomcat\bin) Note: *This file is not written to the disk until > the application server exits*. See below for how to work around this. > > Now that you know where the cobertura.ser file is, you should modify your > deploy step so that it moves the original cobertura.ser to the appropriate > directory in your application server, and then moves it back when finished > testing. Then run cobertura-report. > > I'm using JBoss. When I stop the server, the coverage data file is not > written. Or the coverage data file is 0 bytes. Or cobertura-report and > cobertura-merge complain that the coverage data file is invalid (possibly > throwing an EOFException). > > Cobertura only writes the coverage data file at shutdown. It does this by > adding a shutdown hook withRuntime.getRuntime().addShutdownHook(). JBoss > has its own shutdown hook that calls System.halt()when its finished. If > the JBoss shutdown hook finishes before the Cobertura shutdown hook, then > the call to System.halt()causes the JVM to halt and the cobertura.ser > file will be incomplete. > > To fix this, set -Djboss.shutdown.forceHalt=falsewhen starting JBoss. > > > > On Wed, Aug 8, 2012 at 6:32 PM, Rami Vaknin <rv...@re...> wrote: > >> Hi, >> >> I'm trying to use cobertura using ant task, I get only 0% coverage due >> to the following error which occurs when shuting down jvm for cobertura >> to flush changes into cobertura.ser: >> >> 01:32:24,187 ERROR [stderr] Unable to get lock channel for >> /cobertura.ser.lock: cobertura.ser.lock (Permission denied) >> >> Could you please explain: >> >> 1. Why the lock file is created on / while the cobertura.ser is in >> /usr/share/blahblah (misconfiguration?), what defines the lock file >> location >> 2. Which process/component is trying to create that lock file? >> >> Note that I found 2 old email threads regarding this issue but I >> couldn't understand how to solve that from the threads solutions. >> >> -- >> >> Thanks, >> >> Rami Vaknin, QE @ Red Hat, TLV, IL. >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Cobertura-devel mailing list >> Cob...@li... >> https://lists.sourceforge.net/lists/listinfo/cobertura-devel >> > > > > -- > Thanks and Best Regards > > Sakthivel Kumar > > nsa...@gm... > > > > -- > > Thanks, > > Rami Vaknin, QE @ Red Hat, TLV, IL. > > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: Rami V. <rv...@re...> - 2012-08-09 07:43:10
|
On 08/09/2012 06:25 AM, *** From Sakthivel Kumar*** wrote: > > Hello Rami. > Are you testing your applicaiton using JUnit or is it automation testing? > If so, what kind of application server you are using. External server > or local server? Thanks for the quick response. My application is running under jboss and I'm testing my application using automation test. Also the cobertura instrumentation and report is done via a script. I already use the : "-Dnet.sourceforge.cobertura.datafile=/usr/share/jbossas/bin/cobertura.ser" while starting jboss server so I can't find why the creation of the lock file is in /cobertura.ser.lock. > Also please go to below link and read under heading > http://cobertura.sourceforge.net/faq.html > > > Usage > > When I generate coverage reports, why do they always show 100% > coverage everywhere? > > When I generate coverage reports, why do they always show 0% coverage > everywhere? > > Also read below item in the same link. You may get some pointers. > Hope this helps. > Good luck > Sakthi > > > Using Cobertura with a Web Application > > I have automated tests that use HttpUnit/HtmlUnit/Empirix/Rational > Robot, can I use Cobertura? > > Yes! The process is a bit more involved, but the concept is the same. > First instrument your compiled classes. Then create your war file. > Then deploy the war file into your application server (Tomcat, JBoss, > WebLogic, WebSphere, etc). Now run your tests. > > As your classes are accessed, they will create a "cobertura.ser" file > on the disk. You may need to dig around a bit to find it. Cobertura > puts this file in what it considers to be the current working > directory. Typically this is the directory that the application server > was started from (for example, |C:\Tomcat\bin|) Note: *This file is > not written to the disk until the application server exits*. See below > for how to work around this. > > Now that you know where the cobertura.ser file is, you should modify > your deploy step so that it moves the original cobertura.ser to the > appropriate directory in your application server, and then moves it > back when finished testing. Then run cobertura-report. > > > I'm using JBoss. When I stop the server, the coverage data file is not > written. Or the coverage data file is 0 bytes. Or cobertura-report and > cobertura-merge complain that the coverage data file is invalid > (possibly throwing an EOFException). > > Cobertura only writes the coverage data file at shutdown. It does this > by adding a shutdown hook > with|Runtime.getRuntime().addShutdownHook()|. JBoss has its own > shutdown hook that calls |System.halt()|when its finished. If the > JBoss shutdown hook finishes before the Cobertura shutdown hook, then > the call to |System.halt()|causes the JVM to halt and the > cobertura.ser file will be incomplete. > > To fix this, set |-Djboss.shutdown.forceHalt=false|when starting JBoss. > > > > On Wed, Aug 8, 2012 at 6:32 PM, Rami Vaknin <rv...@re... > <mailto:rv...@re...>> wrote: > > Hi, > > I'm trying to use cobertura using ant task, I get only 0% coverage due > to the following error which occurs when shuting down jvm for > cobertura > to flush changes into cobertura.ser: > > 01:32:24,187 ERROR [stderr] Unable to get lock channel for > /cobertura.ser.lock: cobertura.ser.lock (Permission denied) > > Could you please explain: > > 1. Why the lock file is created on / while the cobertura.ser is in > /usr/share/blahblah (misconfiguration?), what defines the lock > file location > 2. Which process/component is trying to create that lock file? > > Note that I found 2 old email threads regarding this issue but I > couldn't understand how to solve that from the threads solutions. > > -- > > Thanks, > > Rami Vaknin, QE @ Red Hat, TLV, IL. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > <mailto:Cob...@li...> > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > > > > > -- > Thanks and Best Regards > > Sakthivel Kumar > > nsa...@gm... <mailto:nsa...@gm...> -- Thanks, Rami Vaknin, QE @ Red Hat, TLV, IL. |
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-09 03:25:57
|
Hello Rami. Are you testing your applicaiton using JUnit or is it automation testing? If so, what kind of application server you are using. External server or local server? Also please go to below link and read under heading http://cobertura.sourceforge.net/faq.html Usage When I generate coverage reports, why do they always show 100% coverage everywhere? When I generate coverage reports, why do they always show 0% coverage everywhere? Also read below item in the same link. You may get some pointers. Hope this helps. Good luck Sakthi Using Cobertura with a Web Application I have automated tests that use HttpUnit/HtmlUnit/Empirix/Rational Robot, can I use Cobertura? Yes! The process is a bit more involved, but the concept is the same. First instrument your compiled classes. Then create your war file. Then deploy the war file into your application server (Tomcat, JBoss, WebLogic, WebSphere, etc). Now run your tests. As your classes are accessed, they will create a "cobertura.ser" file on the disk. You may need to dig around a bit to find it. Cobertura puts this file in what it considers to be the current working directory. Typically this is the directory that the application server was started from (for example, C:\Tomcat\bin) Note: *This file is not written to the disk until the application server exits*. See below for how to work around this. Now that you know where the cobertura.ser file is, you should modify your deploy step so that it moves the original cobertura.ser to the appropriate directory in your application server, and then moves it back when finished testing. Then run cobertura-report. I'm using JBoss. When I stop the server, the coverage data file is not written. Or the coverage data file is 0 bytes. Or cobertura-report and cobertura-merge complain that the coverage data file is invalid (possibly throwing an EOFException). Cobertura only writes the coverage data file at shutdown. It does this by adding a shutdown hook withRuntime.getRuntime().addShutdownHook(). JBoss has its own shutdown hook that calls System.halt()when its finished. If the JBoss shutdown hook finishes before the Cobertura shutdown hook, then the call to System.halt()causes the JVM to halt and the cobertura.ser file will be incomplete. To fix this, set -Djboss.shutdown.forceHalt=falsewhen starting JBoss. On Wed, Aug 8, 2012 at 6:32 PM, Rami Vaknin <rv...@re...> wrote: > Hi, > > I'm trying to use cobertura using ant task, I get only 0% coverage due > to the following error which occurs when shuting down jvm for cobertura > to flush changes into cobertura.ser: > > 01:32:24,187 ERROR [stderr] Unable to get lock channel for > /cobertura.ser.lock: cobertura.ser.lock (Permission denied) > > Could you please explain: > > 1. Why the lock file is created on / while the cobertura.ser is in > /usr/share/blahblah (misconfiguration?), what defines the lock file > location > 2. Which process/component is trying to create that lock file? > > Note that I found 2 old email threads regarding this issue but I > couldn't understand how to solve that from the threads solutions. > > -- > > Thanks, > > Rami Vaknin, QE @ Red Hat, TLV, IL. > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: Rami V. <rv...@re...> - 2012-08-08 23:32:41
|
Hi, I'm trying to use cobertura using ant task, I get only 0% coverage due to the following error which occurs when shuting down jvm for cobertura to flush changes into cobertura.ser: 01:32:24,187 ERROR [stderr] Unable to get lock channel for /cobertura.ser.lock: cobertura.ser.lock (Permission denied) Could you please explain: 1. Why the lock file is created on / while the cobertura.ser is in /usr/share/blahblah (misconfiguration?), what defines the lock file location 2. Which process/component is trying to create that lock file? Note that I found 2 old email threads regarding this issue but I couldn't understand how to solve that from the threads solutions. -- Thanks, Rami Vaknin, QE @ Red Hat, TLV, IL. |
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-08 22:12:16
|
Hello Cobertura users.
I have below *coverage task 1*, to generate cobertura report.
----------------------------------------------------
<target name="Html-coverage-report">
<!-- Generate a series of HTML files containing the coverage Data in a
user-readable form using nested source filesets.-->
<echo>=== HTML CODE COVERAGE REPORT ===</echo>
<cobertura-report format="html" destdir="${coverage.html.dir}" >
<fileset dir="C:/Documents and
Settings/m095351/IBM/rationalsdp/workspace/QReads">
<include name="**/*.java" />
<exclude name="Unittest/*.java" />
<exclude name="Unittest/junit/*.java" />
</fileset>
</cobertura-report>
<echo>Done compiling Html-coverage-report.</echo>
</target>
-------------------------------------------------------------------------------------
The above task generated a good report, as expected.
Then i modified the same coverage task as *coverage task2* to remove the *
fileset* part as below ,want to create an empty report and run the task..
*<target name="Html-coverage-report">
<!-- Generate a series of HTML files containing the coverage Data in a
user-readable form using nested source filesets.-->
<echo>=== HTML CODE COVERAGE REPORT ===</echo>
<cobertura-report format="html" destdir="${coverage.html.dir}" >*
*
</cobertura-report>
<echo>Done compiling Html-coverage-report.</echo>
</target>*
The above *coverage task2 *should create empty report. Instead, i get
report generated properly with all my packages as when i run the *coverage
task 1 *.
I think the report refers to Internet explorer cache and brings the
original report. I went to IE and clear browser history and run report. No
luck. Any idea how to clear the cache and genearte updated coverage
report.?
Your help is highly appreciated.
thanks
Sakthi.
|
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-03 23:15:42
|
John: Thanks for explanation. I did the same as you explained for before executing my test. To be more clear, after automated test is completed, i get updated client cobertura and server cobertura.ser files. And i merged these two files to get one cobertura.ser file to use this in report generation. Hope this is the correct process i am doing to get good coverage. Please correct me if i am wrong. But after merge, the cobertura.ser file created, if not equal to total of client and server size files, at least it should be greater than *cobertura.ser file with size 4,615 kb.? *At least may be greater than 5,000Kb in my case. For better understanding, please some pointer on what is really happening during merge task run ? Thanks Sakthi On Fri, Aug 3, 2012 at 5:20 PM, John W. Lewis <Joh...@sa...> wrote: > ** ** > > You should probably take the cobertura.ser file that is produced during > instrumentation and copy them over to where the client and server > cobertura.ser files are. Then, run your tests. The cobertura.ser file > will not change size. > **** > > ** ** > > The cobertura.ser file has all the information on all the classes such as > line numbers and conditionals on each line. There are counts for these. > The client and server files are different because cobertura is > “discovering” all the class information as the code is executed. Since > there is overlap between what is discovered on the client and on the > server, you would not expect the merge to be a sum of the two files.**** > > ** ** > > Like I said, the best thing to do is use the cobertura.ser file that was > produced during instrumentation. Cobertura discovers all the class data at > that time.**** > > ** ** > > John**** > > ** ** > > ** ** > > *From:* *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > *Sent:* Friday, August 03, 2012 6:11 PM > *To:* John W. Lewis > *Cc:* Zschocke, Florian; cob...@li... > *Subject:* Total size of merge file of cobertura file created is not > total with client and server cobertura file size.**** > > ** ** > > John:**** > > **** > > After running my automated tests, i got *client cobertura.ser file with > size 4,615 kb*, and server *cobertura.ser as 2226 kb*. I did merge using > cobertura merge task and got cobertura.ser file as* 4615 kb.* Is this > file size correct.? Because i was expecting a total of *client + server, > 4,615+2,226 = close to 6,841 KB*.**** > > **** > > Your comments please. Is my cobertura merge task working properly?**** > > Thanks > Sakthi.**** > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: John W. L. <Joh...@sa...> - 2012-08-03 22:20:47
|
You should probably take the cobertura.ser file that is produced during instrumentation and copy them over to where the client and server cobertura.ser files are. Then, run your tests. The cobertura.ser file will not change size. The cobertura.ser file has all the information on all the classes such as line numbers and conditionals on each line. There are counts for these. The client and server files are different because cobertura is "discovering" all the class information as the code is executed. Since there is overlap between what is discovered on the client and on the server, you would not expect the merge to be a sum of the two files. Like I said, the best thing to do is use the cobertura.ser file that was produced during instrumentation. Cobertura discovers all the class data at that time. John From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] Sent: Friday, August 03, 2012 6:11 PM To: John W. Lewis Cc: Zschocke, Florian; cob...@li... Subject: Total size of merge file of cobertura file created is not total with client and server cobertura file size. John: After running my automated tests, i got client cobertura.ser file with size 4,615 kb, and server cobertura.ser as 2226 kb. I did merge using cobertura merge task and got cobertura.ser file as 4615 kb. Is this file size correct.? Because i was expecting a total of client + server, 4,615+2,226 = close to 6,841 KB. Your comments please. Is my cobertura merge task working properly? Thanks Sakthi. |
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-03 22:11:25
|
John: After running my automated tests, i got *client cobertura.ser file with size 4,615 kb*, and server *cobertura.ser as 2226 kb*. I did merge using cobertura merge task and got cobertura.ser file as* 4615 kb.* Is this file size correct.? Because i was expecting a total of *client + server, 4,615+2,226 = close to 6,841 KB*. Your comments please. Is my cobertura merge task working properly? Thanks Sakthi. |
The working directory of the server.
From: Sakthivel Kumar [mailto:nsa...@gm...]
Sent: Thursday, August 02, 2012 3:42 PM
To: Zschocke, Florian; cob...@li...
Subject: Re: [Cobertura-devel] Help needed. Getting error. [cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
Florian.
Thanks for this info. In server, by default in which directory cobertura.ser will be created.?
Thanks
Sakthi.
Sent from my Palm Pixi on the Now Network from Sprint
________________________________
On Aug 2, 2012 12:52 AM, Zschocke, Florian <Flo...@cy...<mailto:Flo...@cy...>> wrote:
Not every .ser file is a cobertura file. Those are just serialization files created by some other module. You need to find the cobertura.ser file. The is only one.
From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...]<mailto:[mailto:nsa...@gm...]>
Sent: Thursday, August 02, 2012 6:01 AM
To: John W. Lewis
Cc: Zschocke, Florian; cob...@li...<mailto:cob...@li...>
Subject: Help needed. Getting error. [cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
John:
After running my automation tests, i went to AIX server and got several .ser files.
Using below merge build file, i tried to create single .ser file in order to use it for coverage report.
<cobertura-merge >
<fileset dir="${coberturaSerFromAIXServer.dir}">
<include name="QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/*.ser"/>
<include name="QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/*.ser" />
</fileset>
</cobertura-merge>
But compliation failed with following error.
Buildfile: C:\buildCobertraMergeServer.xml
init:
[echo] MHD: Inside ... init of QReadsCoberturaMerge...
[echo] MHD: Done... init of QReadsCoberturaMerge...
merge:
[cobertura-merge] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura-merge] Cobertura: Loaded information on 574 classes.
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1521755581.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2369019016.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2750309912.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2833940874.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2880000903.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___4208528214.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___455826484.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___689659379.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertu
[cobertura-merge] Cobertura: Saved information on 574 classes.
[cobertura-merge] Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook
QReadsCoberturaMerge:
BUILD SUCCESSFUL
Total time: 6 seconds
I searched google and could not find any pointers. Please take a look and help.
I appreciate it.
Thanks
Sakthi
|
Florian.
Thanks for this info. In server, by default in which directory cobertura.ser will be created.?
Thanks
Sakthi.
Sent from my Palm Pixi on the Now Network from Sprint
On Aug 2, 2012 12:52 AM, Zschocke, Florian <Flo...@cy...> wrote:
Not every .ser file is a cobertura file. Those are just serialization files created by some other module. You need to find the cobertura.ser file.
The is only one.
From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...]
Sent: Thursday, August 02, 2012 6:01 AM
To: John W. Lewis
Cc: Zschocke, Florian; cob...@li...
Subject: Help needed. Getting error. [cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
John:
After running my automation tests, i went to AIX server and got several .ser files.
Using below merge build file, i tried to create single .ser file in order to use it for coverage report.
<cobertura-merge >
<fileset dir="${coberturaSerFromAIXServer.dir}">
<include name="QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/*.ser"/>
<include name="QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/*.ser" />
</fileset>
</cobertura-merge>
But compliation failed with following error.
Buildfile: C:\buildCobertraMergeServer.xml
init:
[echo] MHD: Inside ... init of QReadsCoberturaMerge...
[echo] MHD: Done... init of QReadsCoberturaMerge...
merge:
[cobertura-merge] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura-merge] Cobertura: Loaded information on 574 classes.
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1521755581.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2369019016.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2750309912.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2833940874.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2880000903.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___4208528214.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___455826484.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___689659379.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertu
[cobertura-merge] Cobertura: Saved information on 574 classes.
[cobertura-merge] Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook
QReadsCoberturaMerge:
BUILD SUCCESSFUL
Total time: 6 seconds
I searched google and could not find any pointers. Please take a look and help.
I appreciate it.
Thanks
Sakthi
|
Not every .ser file is a cobertura file. Those are just serialization files created by some other module. You need to find the cobertura.ser file. The is only one.
From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...]
Sent: Thursday, August 02, 2012 6:01 AM
To: John W. Lewis
Cc: Zschocke, Florian; cob...@li...
Subject: Help needed. Getting error. [cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
John:
After running my automation tests, i went to AIX server and got several .ser files.
Using below merge build file, i tried to create single .ser file in order to use it for coverage report.
<cobertura-merge >
<fileset dir="${coberturaSerFromAIXServer.dir}">
<include name="QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/*.ser"/>
<include name="QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/*.ser" />
<include name="QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/*.ser" />
</fileset>
</cobertura-merge>
But compliation failed with following error.
Buildfile: C:\buildCobertraMergeServer.xml
init:
[echo] MHD: Inside ... init of QReadsCoberturaMerge...
[echo] MHD: Done... init of QReadsCoberturaMerge...
merge:
[cobertura-merge] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[cobertura-merge] Cobertura: Loaded information on 574 classes.
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1521755581.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2369019016.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2750309912.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2833940874.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2880000903.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___4208528214.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___455826484.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___689659379.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___1865883493.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___2339043118.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___4108232363.ser: invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\xpt___1147241821.ser: invalid stream header: 3C3F786D
[cobertu
[cobertura-merge] Cobertura: Saved information on 574 classes.
[cobertura-merge] Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook
QReadsCoberturaMerge:
BUILD SUCCESSFUL
Total time: 6 seconds
I searched google and could not find any pointers. Please take a look and help.
I appreciate it.
Thanks
Sakthi
|
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-02 04:01:06
|
John:
After running my automation tests, i went to AIX server and got several*.ser
* files.
Using below merge build file, i tried to create single .ser file in order
to use it for coverage report.
<cobertura-merge >
<fileset dir="${coberturaSerFromAIXServer.dir}">
<include
name="QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/*.ser" />
<include
name="QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/*.ser" />
<include
name="QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/*.ser" />
<include
name="QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/*.ser" />
<include
name="QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/*.ser"/>
<include
name="QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/*.ser" />
<include
name="QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/*.ser" />
</fileset>
</cobertura-merge>
But *compliation failed* with following error.
Buildfile: C:\buildCobertraMergeServer.xml
init:
[echo] MHD: Inside ... init of QReadsCoberturaMerge...
[echo] MHD: Done... init of QReadsCoberturaMerge...
merge:
[cobertura-merge] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See
COPYRIGHT file
[cobertura-merge] Cobertura: Loaded information on 574 classes.
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___1865883493.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___2339043118.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\plg___4108232363.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1147241821.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___1521755581.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2369019016.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2750309912.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2833940874.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___2880000903.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___4208528214.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___455826484.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\AdminServices_ei01\_extensionregistry\xpt___689659379.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___1865883493.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___2339043118.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\plg___4108232363.ser:
invalid stream header: 3C3F786D
[cobertura-merge] Cobertura: Error reading file
C:\coberturaSerFromAIXServer\QReads_qrd1ei01_node1\CIGA_ei01\_extensionregistry\xpt___1147241821.ser:
invalid stream header: 3C3F786D
[cobertu
[cobertura-merge] Cobertura: Saved information on 574 classes.
[cobertura-merge] Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook
QReadsCoberturaMerge:
BUILD SUCCESSFUL
Total time: 6 seconds
I searched google and could not find any pointers. Please take a look and
help.
I appreciate it.
Thanks
Sakthi
|
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-08-01 21:11:43
|
John: After my automation finish testing my application, i see 'cobertura.ser' with latest time stamp got created in my local C:\Working directory with same size as instrumented 'cobertura.ser'. Then i stopped the AIX app server and searched for the 'cobertura.ser' file on the server. My question. 1) On the server, will i see one *'cobertura.ser'* file with same time stamp will created as my client cobertura.ser? 2) Or will there be lots of *'xxxxxx.ser'* file in the server will be generated and i need to take only relevent 'xxxx.ser' file with particular time stamp, *merge* all those .ser and use it to generate good coverage report ? Right now i see lots of *'xxxxxx.ser'* file in the server getting generated. Please see below and let me know you thoughts. Thanks Sakthi. -rw-r--r-- 1 webspher web 638 Jul 05 07:59 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 07:59 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 07:59 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/AdminServices_ei01/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei01/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:00 ./temp/QReads_qrd1ei01_node1/CIGA_ei02/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QREADSAPI_ei01/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 10 12:37 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 10 12:37 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 10 12:37 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 10 12:38 ./temp/QReads_qrd1ei01_node1/QReadsLT_ei01/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei01/_extensionregistry/xpt___689659379.ser -rw-r--r-- 1 webspher web 638 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/plg___1865883493.ser -rw-r--r-- 1 webspher web 807 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/plg___2339043118.ser -rw-r--r-- 1 webspher web 759 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/plg___4108232363.ser -rw-r--r-- 1 webspher web 419 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___1147241821.ser -rw-r--r-- 1 webspher web 406 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___1521755581.ser -rw-r--r-- 1 webspher web 410 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___2369019016.ser -rw-r--r-- 1 webspher web 415 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___2750309912.ser -rw-r--r-- 1 webspher web 402 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___2833940874.ser -rw-r--r-- 1 webspher web 432 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___2880000903.ser -rw-r--r-- 1 webspher web 412 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___4208528214.ser -rw-r--r-- 1 webspher web 421 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___455826484.ser -rw-r--r-- 1 webspher web 425 Jul 05 08:02 ./temp/QReads_qrd1ei01_node1/QReads_ei02/_extensionregistry/xpt___689659379.ser On Mon, Jul 30, 2012 at 9:11 AM, John W. Lewis <Joh...@sa...> wrote: > ** ** > > It is actually coberturaFlush.war. Deploy it to your web server similar > to the way you would any war.**** > > ** ** > > When you want to flush the data to the cobertura.ser file, just invoke:*** > * > > ** ** > > http://<HOST>:<PORT>/coberturaFlush/flushCobertura**** > > ** ** > > John**** > > ** ** > > ** ** > > *From:* *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > *Sent:* Monday, July 30, 2012 9:54 AM > *To:* John W. Lewis > *Cc:* Zschocke, Florian; cob...@li... > *Subject:* Details to get cobertura.ser file without stopping the server > and to deploy the flushCobertura.war. [Cobertura-devel] Question regarding > creation of cobertura.ser file after server shut down.**** > > ** ** > > Sounds good. Please send me all the details to get cobertura.ser file > without stopping the server and how to deploy the flushCobertura.war.**** > > **** > > I appreciate it.**** > > **** > > Thanks.**** > > **** > > > **** > > On Mon, Jul 30, 2012 at 8:20 AM, John W. Lewis <Joh...@sa...> > wrote:**** > > > There are also ways to get the server to dump the cobertura.ser file > without stopping the server. The FAQ has one, and if it is a webapp > server, you can deploy the flushCobertura.war. I can send details if you > need them.**** > > > -----Original Message----- > From: Zschocke, Florian [mailto:Flo...@cy...] > Sent: Monday, July 30, 2012 7:54 AM > To: cob...@li...**** > > Subject: Re: [Cobertura-devel] Question regarding creation of > cobertura.ser file after server shut down. > > > From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > > Sent: Sunday, July 29, 2012 11:27 PM > > > > a) Is this means, another cobertura.ser file will be getting created > > on the AIX server ( this is the server my application is running) > > running in an external server box directory apart from the > > cobertura.ser file getting created in my local C:\WorkingDir .? > > Yes. > > > And do i need to go to server, stop the server and grab another > > cobertura.ser and merge with cobertura.ser created on my working > > directory and use in my report generation. to get good coverage report? > > Yes. > > With your local cobertura.ser file you are only measuring and reporting on > your client. You need the cobertura.ser file from the server, too, if you > want to report on the code coverage of the server. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel**** > > > > > -- > Thanks and Best Regards > > Sakthivel Kumar > > nsa...@gm...**** > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: John W. L. <Joh...@sa...> - 2012-07-30 14:11:35
|
It is actually coberturaFlush.war. Deploy it to your web server similar to the way you would any war. When you want to flush the data to the cobertura.ser file, just invoke: http://<HOST>:<PORT>/coberturaFlush/flushCobertura<http://%3cHOST%3e:%3cPORT%3e/coberturaFlush/flushCobertura> John From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] Sent: Monday, July 30, 2012 9:54 AM To: John W. Lewis Cc: Zschocke, Florian; cob...@li... Subject: Details to get cobertura.ser file without stopping the server and to deploy the flushCobertura.war. [Cobertura-devel] Question regarding creation of cobertura.ser file after server shut down. Sounds good. Please send me all the details to get cobertura.ser file without stopping the server and how to deploy the flushCobertura.war. I appreciate it. Thanks. On Mon, Jul 30, 2012 at 8:20 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote: There are also ways to get the server to dump the cobertura.ser file without stopping the server. The FAQ has one, and if it is a webapp server, you can deploy the flushCobertura.war. I can send details if you need them. -----Original Message----- From: Zschocke, Florian [mailto:Flo...@cy...<mailto:Flo...@cy...>] Sent: Monday, July 30, 2012 7:54 AM To: cob...@li...<mailto:cob...@li...> Subject: Re: [Cobertura-devel] Question regarding creation of cobertura.ser file after server shut down. > From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...<mailto:nsa...@gm...>] > Sent: Sunday, July 29, 2012 11:27 PM > > a) Is this means, another cobertura.ser file will be getting created > on the AIX server ( this is the server my application is running) > running in an external server box directory apart from the > cobertura.ser file getting created in my local C:\WorkingDir .? Yes. > And do i need to go to server, stop the server and grab another > cobertura.ser and merge with cobertura.ser created on my working > directory and use in my report generation. to get good coverage report? Yes. With your local cobertura.ser file you are only measuring and reporting on your client. You need the cobertura.ser file from the server, too, if you want to report on the code coverage of the server. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cobertura-devel mailing list Cob...@li...<mailto:Cob...@li...> https://lists.sourceforge.net/lists/listinfo/cobertura-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cobertura-devel mailing list Cob...@li...<mailto:Cob...@li...> https://lists.sourceforge.net/lists/listinfo/cobertura-devel -- Thanks and Best Regards Sakthivel Kumar nsa...@gm...<mailto:nsa...@gm...> |
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-07-30 13:54:09
|
Sounds good. Please send me all the details to get cobertura.ser file without stopping the server and how to deploy the flushCobertura.war. I appreciate it. Thanks. On Mon, Jul 30, 2012 at 8:20 AM, John W. Lewis <Joh...@sa...> wrote: > > There are also ways to get the server to dump the cobertura.ser file > without stopping the server. The FAQ has one, and if it is a webapp > server, you can deploy the flushCobertura.war. I can send details if you > need them. > > -----Original Message----- > From: Zschocke, Florian [mailto:Flo...@cy...] > Sent: Monday, July 30, 2012 7:54 AM > To: cob...@li... > Subject: Re: [Cobertura-devel] Question regarding creation of > cobertura.ser file after server shut down. > > > From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > > Sent: Sunday, July 29, 2012 11:27 PM > > > > a) Is this means, another cobertura.ser file will be getting created > > on the AIX server ( this is the server my application is running) > > running in an external server box directory apart from the > > cobertura.ser file getting created in my local C:\WorkingDir .? > > Yes. > > > And do i need to go to server, stop the server and grab another > > cobertura.ser and merge with cobertura.ser created on my working > > directory and use in my report generation. to get good coverage report? > > Yes. > > With your local cobertura.ser file you are only measuring and reporting on > your client. You need the cobertura.ser file from the server, too, if you > want to report on the code coverage of the server. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: *** F. S. Kumar*** <nsa...@gm...> - 2012-07-30 13:49:47
|
Florian: Thank you very much. Your answers make sense to me now. I will try it. Thanks Sakthi. On Mon, Jul 30, 2012 at 6:54 AM, Zschocke, Florian < Flo...@cy...> wrote: > > From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > > Sent: Sunday, July 29, 2012 11:27 PM > > > > a) Is this means, another cobertura.ser file will be getting created > > on the AIX server ( this is the server my application is running) running > > in an external server box directory apart from the cobertura.ser file > getting > > created in my local C:\WorkingDir .? > > Yes. > > > And do i need to go to server, stop the server and grab another > cobertura.ser > > and merge with cobertura.ser created on my working directory and use in > my > > report generation. to get good coverage report? > > Yes. > > With your local cobertura.ser file you are only measuring and reporting on > your client. You need the cobertura.ser file from the server, too, if you > want to report on the code coverage of the server. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > -- Thanks and Best Regards Sakthivel Kumar nsa...@gm... |
|
From: John W. L. <Joh...@sa...> - 2012-07-30 13:20:18
|
There are also ways to get the server to dump the cobertura.ser file without stopping the server. The FAQ has one, and if it is a webapp server, you can deploy the flushCobertura.war. I can send details if you need them. -----Original Message----- From: Zschocke, Florian [mailto:Flo...@cy...] Sent: Monday, July 30, 2012 7:54 AM To: cob...@li... Subject: Re: [Cobertura-devel] Question regarding creation of cobertura.ser file after server shut down. > From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > Sent: Sunday, July 29, 2012 11:27 PM > > a) Is this means, another cobertura.ser file will be getting created > on the AIX server ( this is the server my application is running) > running in an external server box directory apart from the > cobertura.ser file getting created in my local C:\WorkingDir .? Yes. > And do i need to go to server, stop the server and grab another > cobertura.ser and merge with cobertura.ser created on my working > directory and use in my report generation. to get good coverage report? Yes. With your local cobertura.ser file you are only measuring and reporting on your client. You need the cobertura.ser file from the server, too, if you want to report on the code coverage of the server. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cobertura-devel mailing list Cob...@li... https://lists.sourceforge.net/lists/listinfo/cobertura-devel |
|
From: Zschocke, F. <Flo...@cy...> - 2012-07-30 11:54:28
|
> From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] > Sent: Sunday, July 29, 2012 11:27 PM > > a) Is this means, another cobertura.ser file will be getting created > on the AIX server ( this is the server my application is running) running > in an external server box directory apart from the cobertura.ser file getting > created in my local C:\WorkingDir .? Yes. > And do i need to go to server, stop the server and grab another cobertura.ser > and merge with cobertura.ser created on my working directory and use in my > report generation. to get good coverage report? Yes. With your local cobertura.ser file you are only measuring and reporting on your client. You need the cobertura.ser file from the server, too, if you want to report on the code coverage of the server. |
89 messages has been excluded from this view by a project administrator.
