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
|
From: Jeff L. <jef...@gm...> - 2018-08-22 20:15:20
|
Hi, I saw after seeing this issue was wondering if Cobertura was still being maintained? https://github.com/cobertura/cobertura /issues/382 |
From: Gelabert, B. <bar...@gr...> - 2018-06-01 11:20:35
|
Hello, My name is Barbara Gelabert. I work as a software architect at GRIFOLS (Spain). We are currently evaluating different tools for code coverage analysis and I would like to ask for some information regarding your Cobertura <https://github.com/cobertura/cobertura> tool. As for the information in GitHub: · Cobertura 1.9.4.1 is developed with JDK 5. · Cobertura 2.1.0+ is developed with JDK 6. Our questions are: 1) Which Java versions (minimum maximum) is each version of Cobertura capable to analyze? 2) If our source code is developed with JDK 6, which version of Cobertura should we be using? 3) If our source code is developed with JDK 7, which version of Cobertura should we be using? 4) If our source code is developed with JDK 8, which version of Cobertura should we be using? I look forward to your response. Kind regards, Bàrbara Gelabert Grifols SA GH IT Plasma Architecture +34 935712568 Carrer Palou, 6 (P10) 08150, Parets del Vallès, Spain <http://www.grifols.com> www.grifols.com |
From: gagan n. <gag...@gm...> - 2017-05-05 06:26:54
|
I am stuck on instrumentation phase of cobertura. Command , i am using is : D:\cobertura-2.1.1>cobertura-check.bat --basedir D:\classes --destination D:\Cob ertura_Workspace D:\classes has only 1 .class file which i want to instrument. Results are: Cobertura 2.1.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file [INFO] Cobertura: Loaded information on 0 classes. [INFO] Cobertura: Saved information on 0 classes. [INFO] Cobertura: Saved information on 0 classes. |
From: Thai N. <tkn...@us...> - 2017-03-09 00:15:00
|
Hi, I have a some class files in the same jar file, which does not show up in the generated reports. These files are in the same jar file and package as the ones that do show up in the report, and I can see that it look like they were instrumented. Any ideas why some of them are missing completely from the report? Thx. |
From: Benjamin M. <b.m...@gm...> - 2017-01-08 16:25:35
|
Hello everybody, I aim to start contributing to Cobertura in the near future. My intention is to both help fixing bugs and developing new features. Regarding new features, my primary proposition is to add finer granular functionality to ignore lines of code for coverage, since this is what I see is often needed for projects. I am currently trying to build Cobertura from sources, but fail because of failed test cases. I have a fresh checkout of master done today (2017-01-08). "mvn test" in folder "/cobertura" returns: Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - in test.performance.Test1 Results : Failed tests: FunctionalConditionCoverageTest.testConditionCoverage:154->verify:158->verifyXml:181->verifyClass:229->verifyMethod:275 Expected line 22 to be ignored. IgnoreTrivialAntTest.test:104->assertNotIgnored:126->assertNotIgnored:122 getINVOKEVIRTUAL should not be ignored IgnoreTrivialFunctionalTest.ignoreTrivialTest:477->assertNotIgnored:519->assertNotIgnored:515 getINVOKEVIRTUAL should not be ignored SwitchFunctionalTest.noDefaultTest:474->AbstractCoberturaTestCase.assertConditionCoverage:64 expected:<[33% (1/3])> but was:<[25% (1/4])> Tests in error: IgnoreMethodAnnotationAntTest.setUp:19->AbstractCoberturaAntTestCase.executeAntTarget:59 » Build Tests run: 200, Failures: 4, Errors: 1, Skipped: 0 Some info on my build environment: Ubuntu 16.04 64Bit, Kernel 4.4.0-57-generic, Maven 3.3.9, openjdk version "1.8.0_111" I would be glad if somebody takes the time to help me get started! Kind regards, Ben |
From: Ambika K.S <k.a...@gm...> - 2017-01-05 22:47:32
|
I have a class in one project and i am writing the unit test for it in another project how do i do the code coverage for the class using cobertura? i am adding the maven plugin as below: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <executions> <execution> <id>add-source</id> <phase>generate-sources</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <source>..*/src/main/java</source> </sources> </configuration> </execution> </executions> </plugin> |
From: Neeraj B. <nee...@gm...> - 2016-07-11 21:49:47
|
Hi We are working on generating code coverage reports and exporting them to formats suited for popular CI systems like Jenkins. Currently we aren't using the Cobertura tool to compute the coverage since we are working in a programming language it doesn't work with. However, we're looking into the Cobertura output format which has a strong support for commonly used CI systems, making it a popular choice for using it in XML coverage reports. In order to get the output in the correct format, we were trying to find the official schema/DTD for Cobertura. I see there are 4 versions of DTD files given here - https://github.com/cobertura/web/blob/master/htdocs/xml/ Are these different versions of the official DTD for this format? Also,our language only supports line coverage. Bearing that in mind, we were curious to know why the "branch-rate" attribute for the elements is strict and set to #REQUIRED in the DTD files given above. Could we change it to #IMPLIED (maybe in a "coverage-05.dtd"), thus adding more flexibility and extending to systems not requiring details on branch coverage? Looking forward to hearing from you -- Regards Neeraj Badamikar |
From: Steve C. <sch...@gm...> - 2016-07-03 21:07:09
|
I haven't heard of anyone incorporating cobertura with bazel before. I just got done finish reading about bazel and it sounds like an awesome build tool. On Sun, Jul 3, 2016 at 3:53 PM J <mc...@gm...> wrote: > Has anyone worked on incorporating cobertura into bazel? > > If not, I'll be doing it soon; if you want to collaborate, shoot me a note! > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape_______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel > |
From: J <mc...@gm...> - 2016-07-03 19:53:05
|
Has anyone worked on incorporating cobertura into bazel? If not, I'll be doing it soon; if you want to collaborate, shoot me a note! |
From: Ruban S <siv...@gm...> - 2016-06-24 20:39:30
|
Hello, I'm running cobertura report against grails controller which is a sub-class of grail's RestfulController. Even though I see the unit test is executing atleast once for each line, the code coverage report says 0 line coverage. Any idea ? I'm using Grails 3.1.6 with groovy 2.4.5 built using gradle 2.13 Unit test framework - Spock cobertura plugin - 2.3.2 Thanks in advance -Shiva |
From: Leela M. R. <lr...@sa...> - 2016-06-18 11:54:18
|
Team, Im using Cobertuara to generate code coverage. my pom.xml will look like below. <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <configuration> <reportPlugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>findbugs-maven-plugin</artifactId> <version>${findbugs.version}</version> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <version>${cobertura.version}</version> <configuration> <formats> <format>html</format> </formats> </configuration> </plugin> </reportPlugins> </configuration> </plugin> and reporting section will look like <reporting> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>findbugs-maven-plugin</artifactId> <version>${findbugs.version}</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-report-plugin</artifactId> <version>${surefire.reportplugin.version}</version> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <version>${cobertura.version}</version> <configuration> <formats> <format>html</format> </formats> </configuration> </plugin> </plugins> </reporting> My project is multi level project like Top Folder A - Source Folder B - Source Folder C - Test Folder D B, C, D are sub folders of A also B and C are source code folders whereas D is Test folder. Im using maven clean install site command to compile and run tests. I could see reports but coverage is zero. can somebody help me? -- Thanks & Regards, Mahesh |
From: Leela M. R. <lr...@sa...> - 2016-06-18 11:46:30
|
BTW, Im using cobertuara 2.5.1 version. On Sat, Jun 18, 2016 at 4:57 PM, Leela Maheshwara Rao <lr...@sa...> wrote: > Team, > Im using Cobertuara to generate code coverage. my pom.xml will look like > below. > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-site-plugin</artifactId> > > <configuration> > > <reportPlugins> > > <plugin> > > <groupId>org.codehaus.mojo</groupId> > > <artifactId>findbugs-maven-plugin</artifactId> > > <version>${findbugs.version}</version> > > </plugin> > > > <plugin> > > <groupId>org.codehaus.mojo</groupId> > > <artifactId>cobertura-maven-plugin</artifactId> > > <version>${cobertura.version}</version> > > <configuration> > > <formats> > > <format>html</format> > > </formats> > > </configuration> > > </plugin> > > > > </reportPlugins> > > </configuration> > > </plugin> > > > and reporting section will look like > > > <reporting> > > <plugins> > > <plugin> > > <groupId>org.codehaus.mojo</groupId> > > <artifactId>findbugs-maven-plugin</artifactId> > > <version>${findbugs.version}</version> > > </plugin> > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-surefire-report-plugin</artifactId> > > <version>${surefire.reportplugin.version}</version> > > </plugin> > > <plugin> > > <groupId>org.codehaus.mojo</groupId> > > <artifactId>cobertura-maven-plugin</artifactId> > > <version>${cobertura.version}</version> > > <configuration> > > <formats> > > <format>html</format> > > </formats> > > </configuration> > > </plugin> > > > > > </plugins> > > </reporting> > > > My project is multi level project like > > Top Folder A > > - Source Folder B > > - Source Folder C > > - Test Folder D > > B, C, D are sub folders of A also B and C are source code folders whereas > D is Test folder. Im using maven clean install site command to compile and > run tests. I could see reports but coverage is zero. can somebody help me? > > > > > > -- > > Thanks & Regards, > Mahesh > -- Thanks & Regards, Mahesh |
From: Murugan, B. <bav...@wa...> - 2016-05-03 04:31:07
|
Any help on below issue will be helpful. Hi, We have implemented cobertura with jboss 5.1 and did not have any issues. And now we have upgraded for jboss 6.4. When we do instrumentation during build, we have issues with start up of instance.PFB few exceptions from server log. 1.ERROR [org.jboss.msc.service.fail] (MSC service thread 1-31) MSC000001: Failed to start service jboss.deployment.subunit."deployment.ear"."firstmodule.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."deployment.ear"."firstmodule".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "firstmodule" of deployment "deployment.ear". 2.Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.new.taglib.dspjsp.tag with ClassLoader ModuleClassLoader for Module "deployment.deployment.ear.lib/myclasses.jar:main" from Service Module Loader 3.Class Path entry dhbcore.jar in deployment.ear/lib/myclasses.jar does not point to a valid jar for a Class-Path reference. Also please let me know whether we can instrument java files. Because when I try with class or jar files instrumentation works. And for java files it doesn't works. Thanks much !!! |
From: Murugan, B. <bav...@wa...> - 2016-04-25 12:04:16
|
Hi, We have implemented cobertura with jboss 5.1 and did not have any issues. And now we have upgraded for jboss 6.4. When we do instrumentation during build, we have issues with start up of instance.PFB few exceptions from server log. 1.ERROR [org.jboss.msc.service.fail] (MSC service thread 1-31) MSC000001: Failed to start service jboss.deployment.subunit."deployment.ear"."firstmodule.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."deployment.ear"."firstmodule".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "firstmodule" of deployment "deployment.ear". 2.Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.new.taglib.dspjsp.tag with ClassLoader ModuleClassLoader for Module "deployment.deployment.ear.lib/myclasses.jar:main" from Service Module Loader 3.Class Path entry dhbcore.jar in deployment.ear/lib/myclasses.jar does not point to a valid jar for a Class-Path reference. Also please let me know whether we can instrument java files. Because when I try with class or jar files instrumentation works. And for java files it doesn't works. Thanks much !!! Bavithra M |
From: Grzegorz S. <gsl...@gm...> - 2016-01-26 13:40:08
|
Hi Cobertura Team There are two different "coverage-04.dtd" files available: - http://cobertura.sourceforge.net/xml/coverage-04.dtd referenced in Cobertura sources, does not have "complexity" attribute for <method> element, - https://raw.githubusercontent.com/cobertura/cobertura/master/cobertura/src/site/htdocs/xml/coverage-04.dtd - I don't know, where is it on Cobertura site (what's the official URI), has this attribute. 1. What URI should I use in "coverage.xml" files (generated by Scoverage tool)? 2. If the second one, what is proper URI? Regards Grzegorz Slowikowski |
From: Cahangirova G. <gu...@gm...> - 2016-01-15 10:45:58
|
Hi, I am working on a research project and what I need to do is given a test suite to find the coverage information for each test case in the test suite in the xml format. I have run Cobertura and what I get is a very nice report containing overall coverage information for each class without specifying any details about the coverage achieved by each test case. Is there any configurations I can make to get the information I need? Thanks in advance! |
From: Chris V. <cv...@me...> - 2015-08-18 20:12:13
|
Hi all, I have a Maven-based project where I'm using Cobertura 2.1.1 via the Cobertura Maven Plugin 2.7. Tests are being run using PowerMock 1.5.2 (Junit 4.11) and Java 1.7.0_80. The tests are running just fine, but one class appears to have 0% line coverage even though the class' tests are being executed. ... Running com.xxx.apps.commons.jobs.misc.TimeUtilsTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.412 sec - in com.xxx.apps.commons.jobs.misc.TimeUtilsTest ... [INFO] --- cobertura-maven-plugin:2.7:check (default) @ commons-jobs --- [INFO] Cobertura 2.1.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file [INFO] Cobertura: Loaded information on 59 classes. [[ERROR] com.xxx.apps.commons.jobs.misc.TimeUtils failed coverage check. Line coverage rate of 0.0% is below 75.0% ... The <build> section from pom.xml is: <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <version>${cobertura.version}</version> <configuration> <check> <totalBranchRate>90</totalBranchRate> <packageBranchRate>90</packageBranchRate> </check> <instrumentation> <excludes> <exclude>**/*Exception.class</exclude> <exclude>**/JobStatus.class</exclude> <exclude>**/PGPUtils.class</exclude> <exclude>**/LastLineRemover.class</exclude> <exclude>**/EofMarkRemoverStrategy.class</exclude> <exclude>**/MonitorStatusReporter*.class</exclude> <exclude>**/JobConfiguration.class</exclude> </excludes> </instrumentation> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <!-- Use the version from the parent --> <configuration> <argLine>-Xmx1024m -XX:MaxPermSize=1024m</argLine> </configuration> </plugin> </plugins> </build> After playing with this for awhile now, I'm at a bit of a loss for what to do next to continue debugging. The TimeUtils class is showing up in the cobertura.ser file, it's being executed, etc. Any guidance that you can provide would be greatly appreciated! Thanks, Chris |
From: Williams, J. A. <Jef...@gd...> - 2015-06-18 17:41:27
|
If you repeat a test case will the previous results be overwritten or do the output files have a unique naming convention? |
From: Timo <Mai...@gm...> - 2015-05-25 20:07:27
|
Hello again, in the last few weeks, I started implementing my proposed preparation steps. It turns out that recreating the HTMLReport using FreeMarker was the hardest part so far. But I think I did it. Please have a look at my Cobertura fork [1] to see what I've been up to. There is still a lot of work to do and I am still not sure if want I'm doing is in the interest of Cobertura's maintainers. I would appreciate feedback from anyone. Thanks! Timo [1] https://github.com/hzpz/cobertura 2015-05-06 21:58 GMT+02:00 Timo <Mai...@gm...>: > Hello everyone, > > I am currently developing a project using Java 8 and want to check the > code coverage of my tests. As you know, Cobertura does not fully > support Java 8 because JavaNCSS cannot parse Java 8 source code. The > coverage reporting does seem to work flawlessly, however the > complexity calcuation fails with an unpleasant exception from > JavaNCSS. Since I do not care about the complexity reporting right > now, I would like to be able to disable it and use Cobertura for code > coverage reporting only. As I was searching for a way to do that I > discovered this feature in the roadmap [1]. So I thought I would give > the source code of Cobertura a look and see how it could be > implemented. > > First of all, I am not sure I understand all design/architecture > desicions in Cobertura. That being said, here is my rough proposal how > to implement enabling/disabling the code complexity calculator: > > Preparations > - To make Cobertura's reporting flexible and maintainable, I would > like to separate data, view and logic. Currently, the various classes > generating output (e.g. HTMLReport) mix it all together. Let's call > HTMLReport etc. "OutputReports" to distinguish them from > net.sourceforge.cobertura.reporting.Report. > - There should be a class that can hold complexity information, > without any logic. Not the ComplexityCalculator, but something that is > filled using the ComplexityCalculator. This way we can separate logic > from data and OutputReports do not have to know about the > ComplexityCalculator. Let's call this class "ComplexityData". > - Cobertura should use a template engine like Velocity or Freemarker > to generate output. This way we can easily implement reports with or > without complexity information and even "themes" in some future > version. > - There should be a ReportingTask, much like the CheckCoverageTask, > that creates the NativeReport. The ComplexityCalculator and the > ComplexityData object should be created there. Only the ComplexityData > object should be passed to the NativeReport. > > Once the preparations are done, we can implement the switch: > - Add a Metric enum with two values: COVERAGE and COMPLEXITY > - Add a method to the Report interface: hasMetric(Metric) > - Use that method in the ReportFormatStrategy implementations to > decide which OutputReport to use > - Implement OutputReports without complexity information > - Add a method named "coverageOnly" to the DSL which sets an internal boolean. > - When report() is called, the boolean is passed to the ReportingTask > which returns a report with or without complexity information. The > default is to calculate both coverage and complexity to stay API > compatible with earlier versions. > > What do you think? > > Greetings from Germany > Timo > > > [1] https://github.com/cobertura/cobertura/wiki/Roadmap |
From: Timo <Mai...@gm...> - 2015-05-06 19:58:24
|
Hello everyone, I am currently developing a project using Java 8 and want to check the code coverage of my tests. As you know, Cobertura does not fully support Java 8 because JavaNCSS cannot parse Java 8 source code. The coverage reporting does seem to work flawlessly, however the complexity calcuation fails with an unpleasant exception from JavaNCSS. Since I do not care about the complexity reporting right now, I would like to be able to disable it and use Cobertura for code coverage reporting only. As I was searching for a way to do that I discovered this feature in the roadmap [1]. So I thought I would give the source code of Cobertura a look and see how it could be implemented. First of all, I am not sure I understand all design/architecture desicions in Cobertura. That being said, here is my rough proposal how to implement enabling/disabling the code complexity calculator: Preparations - To make Cobertura's reporting flexible and maintainable, I would like to separate data, view and logic. Currently, the various classes generating output (e.g. HTMLReport) mix it all together. Let's call HTMLReport etc. "OutputReports" to distinguish them from net.sourceforge.cobertura.reporting.Report. - There should be a class that can hold complexity information, without any logic. Not the ComplexityCalculator, but something that is filled using the ComplexityCalculator. This way we can separate logic from data and OutputReports do not have to know about the ComplexityCalculator. Let's call this class "ComplexityData". - Cobertura should use a template engine like Velocity or Freemarker to generate output. This way we can easily implement reports with or without complexity information and even "themes" in some future version. - There should be a ReportingTask, much like the CheckCoverageTask, that creates the NativeReport. The ComplexityCalculator and the ComplexityData object should be created there. Only the ComplexityData object should be passed to the NativeReport. Once the preparations are done, we can implement the switch: - Add a Metric enum with two values: COVERAGE and COMPLEXITY - Add a method to the Report interface: hasMetric(Metric) - Use that method in the ReportFormatStrategy implementations to decide which OutputReport to use - Implement OutputReports without complexity information - Add a method named "coverageOnly" to the DSL which sets an internal boolean. - When report() is called, the boolean is passed to the ReportingTask which returns a report with or without complexity information. The default is to calculate both coverage and complexity to stay API compatible with earlier versions. What do you think? Greetings from Germany Timo [1] https://github.com/cobertura/cobertura/wiki/Roadmap |
From: Casper B. <cas...@sy...> - 2015-03-25 08:29:09
|
I realize Cobertura is primarily a Java tool (or rather, byte-code tool) but I'm faced with the issue of Cobertura flagging trivial method calls in a Grails (Groovy) application on JDK7 (see attached screenshot). Without knowing much about Cobertura, I speculate that the problem is in Java's virtual by default (and Groovy's dynamic nature i.e. completely lacking the notion of a final/sealed non-virtual method) which means Cobertura always sees the dispatch VTABLE and thus, a branch! This effectually renders Cobertura useless for reporting branch coverage on our Grails/Groovy code, as it flags way too many false positives. Using the ignoreTrivial=true doesn't seem to change much in this aspect, and I can't find an @Ignore annotion for use with. Am I missing something or does anyone have an advice for how to resolve the situation? Med venlig hilsen / Kind regards Casper Bang Systems Engineer |
From: Shankar R. <sha...@gm...> - 2015-03-05 15:33:05
|
Hi, Of late, we in our team are trying to get cobertura reports generated from selenium tests run out of the production deployment of our JBoss based applications. We use JBoss 6.1.0 for this purpose. For some reason, the server doesn't seem to write into the cobertura.ser file. I followed the steps mentioned in the links at http://blog.avisi.nl/2012/09/25/calculating-the-code-coverage-of-integration-tests/ https://github.com/cobertura/cobertura/wiki/FAQ http://ehc.ac/p/cobertura/mailman/message/25520114/ for this but still not able to get coverage information written into that file. Out of the many suggestions, I tried 1. Starting JBoss from folder where the cobertura.ser file is present (bin folder). 2. Using -Djboss.shutdown.forceHalt=false 3. Using -Dnet.sourceforge.cobertura.datafile=$JBOSS_HOME/bin/cobertura.ser. 4. Ensured cobertura.ser has file permissions at 666 for it to get updated. After adding datafile property, I see the file is being touched by some process (through change in file modified timestamp) but doesn't have coverage information added. (All classes still show 0% coverage) I checked that the machine doesn't have any other cobertura.ser file anywhere besides the one placed by me in the bin directory. I am not so keen on writing the code snippet into our codebase to get cobertura to forcefully write the coverage information here( http://stackoverflow.com/questions/18872871/cobertura-issues-in-writing-ser-files), hence would like to seek suggestions as to what else can I do to generate coverage information serialized into the cobertura.ser file. 1. Is there anyway to debug the status of cobertura on the server. 2. Is there any other work-around to make it serialize without needing to add code to the JBoss runtimes. Any help is appreciated. With Regards Shankar Ramachandran |
From: Sanjay S. <san...@gm...> - 2015-01-22 03:51:26
|
I cant seem to find the solution for this for quite sometime, Can anyone help please- [cobertura-instrument] WARN instrumentClass, Unable to instrument file G:\proj ects\tap\tap-ejb\target\classes\com\tap\findaway\FindawayClientFacto ryImpl.class [cobertura-instrument] java.lang.NullPointerException [cobertura-instrument] at net.sourceforge.cobertura.instrument.tp.ClassMap.appl yOnProjectData(ClassMap.java:364) [cobertura-instrument] at net.sourceforge.cobertura.instrument.CoberturaInstrum enter.instrumentClass(CoberturaInstrumenter.java:187) [cobertura-instrument] at net.sourceforge.cobertura.instrument.CoberturaInstrum enter.instrumentClass(CoberturaInstrumenter.java:121) [cobertura-instrument] at net.sourceforge.cobertura.instrument.CoberturaInstrum enter.addInstrumentationToSingleClass(CoberturaInstrumenter.java:234) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.addInstrume ntationToSingleClass(Main.java:298) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.addInstrume ntation(Main.java:307) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.parseArgume nts(Main.java:399) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.main(Main.j ava:421) [cobertura-instrument] Exception in thread "main" java.lang.NullPointerException [cobertura-instrument] at net.sourceforge.cobertura.coveragedata.CoverageDataFi leHandler.saveCoverageData(CoverageDataFileHandler.java:138) [cobertura-instrument] at net.sourceforge.cobertura.coveragedata.CoverageDataFi leHandler.saveCoverageData(CoverageDataFileHandler.java:115) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.parseArgume nts(Main.java:404) [cobertura-instrument] at net.sourceforge.cobertura.instrument.Main.main(Main.j ava:421) |
From: Sharp, D. L <dav...@kc...> - 2014-12-05 21:15:59
|
Since instrumented code could conceivably be considered a derived work, would the act of instrumenting non-GPL code violate the license? I'm evaluating options for providing code coverage reports on a non-GPL project and would like to make sure I'm not violating the license. Thanks, Dave |
From: Irfan S. <irf...@gm...> - 2014-12-04 05:05:44
|
hi, when is the next official release planned for cobertura?? we are looking for support for java 8 (lambda expression) please let me know asap regards irfan |