Skip to main content

Maven : Create JaCoCo Code Coverage Report

Introduction

In this tutorial we will see how to setup the JaCoCo plugin to generate a code coverage report for a Maven project.

In order to generate a unit test coverage report, we should have sufficient unit test cases in our application. For this tutorial, I am referring to a Maven project which has a string manipulation method.

You can find this project at this GitHub location.

There are a few steps that need to be taken to produce the report.

Install the Maven JaCoCo plugin.

Insert the following code into pom.xml.

<plugin>
    <groupId>org.jacoco</groupId>
    <artifactId>jacoco-maven-plugin</artifactId>
    <version>0.8.2</version>
    <executions>
        <execution>
            <goals>
                <goal>prepare-agent</goal>
            </goals>
        </execution>
        <execution>
            <id>report</id>
            <phase>test</phase>
            <goals>
                <goal>report</goal>
            </goals>
        </execution>
    </executions>
</plugin>


Add a Unit Test

Create a class as "StringUtil.java" and add following snippet

package com.zainabed.tutorials;

public class StringUtil {

    public int findIntegerCount(String input) {
        
        if (input == null) {
            return 0;
        }
        
        int count = 0;
        for (int index = 0; index < input.length(); index++) {
            char character = input.charAt(index);
            if (character >= 48 && character <= 57) {
                count++;
            }
        }
        
        return count;
    }
}


Next, create a unit test class for above class as "StringUtilTest.java".

package com.zainabed.tutorials;

import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertEquals;


class StringUtilTest {

    @Test
    void should_return_count_of_numeric_value() {
        StringUtil stringUtil = new StringUtil();
        String input = "1name34sample;";
        assertEquals(3, stringUtil.findIntegerCount(input));

        input = "namesample";
        assertEquals(0, stringUtil.findIntegerCount(input));
    }
}


Now execute the maven build. It will generate the code coverage report.

mvn clean install


Code coverage result


You can configure different goals of the JaCoCo plugin, such as restricting code coverage percentage.

Our application has 75% branch coverage so far. Let's use the following snippet to configure the coverage limit by setting the execution configuration of the JaCoCo plugin and setting the value to 80%.


<execution>
	<id>coverage-check</id>
	<phase>test</phase>
	<goals>
	    <goal>check</goal>
	</goals>
	<configuration>
	    <rules>
		<rule>
		    <element>CLASS</element>
		    <limits>
		        <limit>
		            <counter>BRANCH</counter>
		            <value>COVEREDRATIO</value>
		            <minimum>80%</minimum>
		        </limit>
		    </limits>
		</rule>
	    </rules>
	</configuration>
</execution>


Now with this configuration build will fail.



We can make the build pass by improving the branch code coverage. Let us update the unit test as follows.

 @Test
    void should_return_zero_for_empty_string() {
        StringUtil stringUtil = new StringUtil();
        assertEquals(0, stringUtil.findIntegerCount(null));
    }


Build the application again

mvn clean install



The report will show the following result.



Conclusion

Code coverage is a useful asset to improve unit testing of applications and JaCoCo facilitates it efficiently.

Comments

Subscribe for latest tutorial updates

* indicates required

Popular posts from this blog

Preload Images Using Javascript

Preload Image is technique which helps browser to render images with minimum delay. Today we will see example of image gallery. Gallery contain 5 images which load images one after another whenever user clicks next and back button. This is a basic image gallery scenario which is used in all possible website, then why we need preloaded images for this gallery? Now a day’s most of website becoming faster and user expectation is increasing. Suppose your website doesn’t use preload image technique for gallery and a user visits any image gallery from Google Plus or Facebook and visits your website gallery. Then that user always prefer those websites rather than yours. Why? Because your website load one image at a time. When user click on next button, then only gallery load image and user has wait till it get loaded. To avoid this situation gallery needs to download all images ...

CSS: How To Create Custom Scrollbar For Webkit Supported Browsers

In this tutorial, we will learn how to create a custom scroll bar using custom CSS styles. Custom scrollbars are becoming increasingly popular, and I'm excited to learn more about them. A scrollbar can be customised for a variety of reasons. The default scrollbar, for example, can make an app's UI look inconsistent across various versions of windows, thus we can benefit from having a single style here. This tutorial will help to create a custom scrollbar. Let's see how One of the most interesting aspects of these scrollbars is that they may be rendered in a variety of styles for different HTML elements on the same webpage. We will see the implementation of such a scrollbar for Webkit-supported browsers. First we will look at the basic CSS properties of the scrollbar. ::-webkit-scrollbar              ::-webkit-scrollbar-thumb        ::-webkit-scrollbar-track  ...

How to enable SQL logs in Spring Boot application?

This tutorial will demonstrate how to enable and disable SQL log statements in a Spring Boot application in order to debug SQL flow. Problem You will frequently need to debug the SQL statement while developing a Spring Boot application with a SQL database. SQL debug logs can assist you figure out what's wrong with JPA statements and whether or not there's a problem with database connectivity. Example  If you've built custom Spring data JPA methods and need to know what SQL statement is being utilized behind them, return repository . findByUsernameIn ( usernames ); Then you can enable Hibernet debug mode to log SQL statements. Solution Update the application.yml file with the Hibernet configuration as logging: level: org: hibernate: DEBUG or application.properties as logging.level.org.hibernate=DEBUG The SQL statement will appear in the application logs after modifying the configuration file and restarting the application. 2022-04-07 08:41...