JUnit Jenkins: The Basics and a Quick Tutorial

What Is the Jenkins JUnit Plugin? 

The Jenkins JUnit plugin integrates testing results from JUnit, a leading Java unit testing framework, with Jenkins, a widely used continuous integration (CI) tool. It allows Jenkins to interpret JUnit test reports, present detailed test results and trends, and integrate them into the build summaries. 

When a build is executed, the plugin processes the JUnit test results, highlighting failing tests or skipped tests. This facilitates quick identification of issues, making it easier for developers to maintain code health and efficiency. 

The Jenkins JUnit plugin improves development workflows by automatically tracking test outcomes over time. This tracking can uncover patterns such as frequently failing tests or fluctuating test stability. By providing this information directly within the Jenkins interface, developers can quickly discover issues and remediate them.

Understanding Jenkins JUnit Plugin Configurations 

The Jenkins JUnit plugin offers configuration options that enable developers to customize how JUnit test results are processed and displayed. Here is an overview of the key configuration parameters:

Test Report XMLs

This parameter specifies the path to JUnit XML files using the Ant glob syntax, such as **/build/test-reports/*.xml. Multiple patterns can be specified, separated by commas. It is essential to ensure that only valid test report files are included in these patterns to avoid processing errors.

Retain Long Standard Output/Error

When enabled, this option retains all standard output or error messages from the test suite in the test results, even if the test passes. By default, Jenkins truncates lengthy output from passing tests to save space. Retaining all output can be useful for debugging, but it can significantly increase Jenkins’ memory consumption.

Health Report Amplification Factor

This factor adjusts the impact of test failures on the build’s health score. The default value is 1.0, but it can be customized. For instance, a factor of 0.5 means that if 10% of tests fail, the build health score would be 95%. Setting the factor to 0.0 disables the impact of test results on the build health score entirely.

Allow Empty Results

Enabling this option prevents the build from failing if test result files are missing or empty. This can be useful to avoid false negatives in cases where the test tool does not exit with an error code when it fails to produce report files. However, it may make it harder to detect misconfigured jobs.

Skip Publishing Checks

If unchecked, the plugin automatically publishes test results to corresponding SCM hosting platforms like GitHub using the Checks API. Disabling this feature can speed up the build process if publishing checks is unnecessary.

Checks Name

When publishing checks is enabled, this option allows specifying a custom name for the checks. If not provided, the default name “Test” is used.

Skip Marking Build Unstable

By default, the plugin marks the build as unstable if at least one test fails. Enabling this option allows the build to be marked as successful even if there are test failures, although the corresponding pipeline node and stage will still be marked as unstable. This can be controlled using the property: skipMarkingBuildUnstable: true.

These configurations provide a framework for integrating JUnit test results with Jenkins, enhancing the visibility and management of test outcomes within the CI/CD pipeline.

Getting Started with the Jenkins JUnit Plugin 

Installing the Plugin

To leverage the Jenkins JUnit plugin for processing JUnit test results, you first need to install it. Follow these steps to install the JUnit plugin in Jenkins:

1. Access plugin management:
   1. Navigate to your Jenkins dashboard.

2. Click on Manage Jenkins in the sidebar.

3. Select Manage Plugins from the menu.

2. Search and install JUnit plugin:
   1. Click on the Available tab to see a list of plugins available for installation.

2. In the search box, type junit to find the JUnit plugin.

3. Once located, check the box next to the JUnit plugin option.
4. Click Install without restart to begin the installation process.

Note: In newer versions of Jenkins, the JUnit plugin is a default plugin that comes pre-installed.

Using the JUnit Plugin in a New Pipeline Project

After installing the JUnit plugin, you can create a new pipeline project that incorporates the plugin. Here’s how to set up a pipeline project:

1. Create new item: From the Jenkins dashboard, click New Item. Enter a name for your project, for instance, MyProject. Select the Pipeline option and click the OK button.

2. Configure the pipeline script: In the project configuration page, scroll down to the Pipeline section.

Paste the following pipeline script into the script area:

pipeline {
    agent any

    stages {
        stage('Build') {
            steps {
                echo 'Building...'
                sh 'mvn clean compile'
            }
        }
        stage('Test') {
            steps {
                echo 'Running Tests...'
                sh 'mvn test'
            }        
        }
        stage('Deploy') {
            steps {
                echo 'Deploying (using rsync)...'
                sh """
                rsync -avz --delete \
                /usr/local/dev/ \
                [email protected]:/usr/local/super_app/
                """
            }
        }
    }

    post {
        always {
            echo 'Cleaning up...'
            sh ‘rm -f tmp/*.dmx’ 

		junit(testResults: 'target/surefire-reports/*.xml', allowEmptyResults: true)
        }
        success {
            echo 'Build succeeded!'
        }
        failure {
            echo 'Build failed!'
        }
    }
}

A few important details about the pipeline script:

• Build stage: Code is compiled on the local machine.
• Test stage: Runs the Maven test  The junit step publishes the test results to Jenkins.
• Deploy  stage: Compiled solution is deployed on the remote server using Linux RSYNC command.
• Post actions: Uses the JUnit plugin to process the test results. The always block ensures that resources are cleaned up,  test results are processed regardless of the build outcome, with allowEmptyResults set to true to prevent the build from failing if no test results are found.

3. Click the “Save” button to save your pipeline configuration.

Quick Tutorial: Recording Tests and Artifacts in Jenkins with JUnit 

Here’s how you can configure Jenkins to record and aggregate JUnit test results, as well as manage artifacts generated during the build process.

Configuring Test Result Collection

To collect test results, ensure your test runner outputs JUnit-style XML reports. Jenkins typically includes the junit step, which processes these reports. If your test runner does not output JUnit-style reports, you can use additional plugins to process other formats.

Here’s an example of a Jenkinsfile using a declarative pipeline to collect test results:

pipeline {
agent any  
stages {  
    stage('Test') {  
        steps {  
            sh './gradlew check'  
        }  
    }  
}  
post {  
    always {  
        junit 'build/reports/**/*.xml'  
    }  
}  
}

In this configuration:

• The Test stage runs the tests using the ./gradlew check command.
• The post section, which runs after the Test stage, uses the junit step to process test results found in the build/reports directory.

This setup allows Jenkins to track test results, calculate trends, and report them. If tests fail, the pipeline will be marked as “UNSTABLE,” indicated by yellow in the Jenkins UI, distinct from a “FAILED” state shown in red. You can also configure the pipeline to skip deployment steps if the build is unstable by using the skipStagesAfterUnstable option.

Archiving Build Artifacts

When tests fail, it’s often necessary to analyze built artifacts locally. Jenkins supports storing these artifacts using the archiveArtifacts step. Here’s how you can configure this in your Jenkinsfile:

pipeline {
    agent any  
    stages {  
        stage('Build') {  
            steps {  
                sh 'rm -f ./temp/*.log && mvn clean install'  
            }  
        }  
        stage('Test') {  
            steps {  
                sh 'mvn test'  
            }  
        }  
    }  
    post {  
        always {  
            archiveArtifacts artifacts: 'target/**/*.jar', fingerprint: true  
            junit 'target/surefire-reports/**/*.xml'  
        }  
    }  
}

In this configuration:

• The Build stage compiles the project.
• The Test stage runs the tests.
• The post section includes two steps:
  • archiveArtifacts stores the JAR files generated during the build, with the fingerprint option enabling tracking of these artifacts.
  • junit processes the test results.

By configuring Jenkins to collect test results and archive artifacts, you streamline the process of diagnosing issues and improving code quality. This setup ensures that critical information is readily available to the development team, enhancing overall efficiency and reliability of the CI/CD pipeline.

Related content: Read our guide to Jenkins pipeline

Codefresh: A Modern Alternative to Jenkins

You can’t get to continuous delivery or deployment without first solving continuous integration. Codefresh automatically creates a Delivery Pipeline, which is a workflow along with the events that trigger it. We’ve added a pipeline creation wizard that will create all the component configurations so you can spend less time with YAML and more time getting work done. 

At the end of the pipeline creation wizard, Codefresh commits the configuration to git and allows its built-in Argo CD instance to deploy them to Kubernetes.

The Delivery pipeline model also allows the creation of a single reusable pipeline that lets DevOps teams build once and use everywhere. Each step in a workflow operates in its own container and pod. This allows pipelines to take advantage of the distributed architecture of Kubernetes to easily scale both on the number of running workflows and within each workflow itself.

Ready to Get Started?

Deploy more and fail less with Codefresh and Argo

Sign Up