code-coverage - w3toppers.com

How would I add an annotation to exclude a method from a jacoco code coverage report?

Since there are no direct answers to this, did a bit of research and came across this PR. https://github.com/jacoco/jacoco/pull/822/files private static boolean matches(final String annotation) { final String name = annotation .substring(Math.max(annotation.lastIndexOf(“https://stackoverflow.com/”), annotation.lastIndexOf(‘$’)) + 1); return name.contains(“Generated”) } You can create any annotation with name containing “Generated”. I’ve created the following in my codebase to … Read more

How to add test coverage to a private constructor?

I don’t entirely agree with Jon Skeet. I think that if you can get an easy win to give you coverage and eliminate the noise in your coverage report, then you should do it. Either tell your coverage tool to ignore the constructor, or put the idealism aside and write the following test and be … Read more

Mocking Java enum to add a value to test fail case

Here is a complete example. The code is almost like your original (just simplified better test validation): public enum MyEnum {A, B} public class Bar { public int foo(MyEnum value) { switch (value) { case A: return 1; case B: return 2; } throw new IllegalArgumentException(“Do not know how to handle ” + value); } … Read more

Android test code coverage with JaCoCo Gradle plugin

Here is how I’m using Jacoco: buildscript { repositories { mavenLocal() mavenCentral() } dependencies { classpath ‘com.android.tools.build:gradle:0.12.+’ classpath ‘org.robolectric:robolectric-gradle-plugin:0.11.+’ } } apply plugin: ‘com.android.application’ apply plugin: ‘robolectric’ apply plugin: ‘jacoco’ android { compileSdkVersion 20 buildToolsVersion “20.0.0” defaultConfig { applicationId “YOUR_PACKAGE_NAME” minSdkVersion 10 targetSdkVersion 20 testHandleProfiling true testFunctionalTest true } buildTypes { debug { testCoverageEnabled false … Read more

LCOV/GCOV branch coverage with C++ producing branches all over the place

The thing is that GCC also records branch information for each line where a scope exit due to some thrown exception is possible (e.g. on Fedora 25 with GCC 6.3.1 and lcov 1.12). The value of this information is limited. The main use case for branch coverage data are complicated if-statements that have a multi-clausal … Read more

Find unused code in a Rails app

Under normal circumstances the approach would be to use your test data for code coverage, but as you say you have parts of your code that are tested but are not used on the production app, you could do something slightly different. Just for clarity first: Don’t trust automatic tools. They will only show you … Read more

Detailed guide on using gcov with CMake/CDash?

I’ve been using https://github.com/bilke/cmake-modules/blob/master/CodeCoverage.cmake successfully. Just followed the guidelines: added the files to my CMAKE_MODULE_PATH directory, added set(CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/CMakeModules) if(CMAKE_COMPILER_IS_GNUCXX) include(CodeCoverage) setup_target_for_coverage(${PROJECT_NAME}_coverage ${PROJECT_TEST_NAME} coverage) endif() in my CMakeLists.txt. I also added manually gcov as a dependency for my target: if(CMAKE_COMPILER_IS_GNUCXX) target_link_libraries(${PROJECT_TEST_NAME} gcov) endif() With this, I just type make my_project_coverage and I get the html … Read more

SONAR – Measure Code Coverage using Cobertura

You configure the Sonar task to upload unit test and cobertura reports generated by other parts of your build logic. This is in contrast to Maven which has a standard build life-cycle that Sonar is able to leverage. Unit test and code coverage The following logic runs the unit tests with cobertura instrumented classes. An … Read more

What is code coverage and how do YOU measure it?

Code coverage is a measurement of how many lines/blocks/arcs of your code are executed while the automated tests are running. Code coverage is collected by using a specialized tool to instrument the binaries to add tracing calls and run a full set of automated tests against the instrumented product. A good tool will give you … Read more

Exclude methods from code coverage with Cobertura

You can exclude classes from instrumentation. Then they should not appear on reports. See exclude statements below. You can also ignore calls to some methods. See ignore statement below. If you are using maven, see maven plugin manual. <configuration> <instrumentation> <ignores> <ignore>com.example.boringcode.*</ignore> </ignores> <excludes> <exclude>com/example/dullcode/**/*.class</exclude> <exclude>com/example/**/*Test.class</exclude> </excludes> </instrumentation> </configuration> And for ant see this. <cobertura-instrument … Read more