JUnit test report publishing in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of JUnit Test Report Publishing in Jenkins

What is the main purpose of publishing JUnit test reports in Jenkins pipelines?

A To automatically fix failing tests during the build

B To display test results and trends in Jenkins UI for easy monitoring

C To deploy the application after tests pass

D To generate code coverage reports from test execution

💡 Hint

Think about what Jenkins shows after tests run.

Publishing JUnit test reports allows Jenkins to parse test results and show them in the UI, helping teams monitor test success and failures over time.

❓ Predict Output

intermediate

Output of Jenkins Pipeline with JUnit Step

Given this Jenkins pipeline snippet, what will Jenkins display after running the tests?

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
      }
    }
  }
}

A Jenkins ignores the test reports and continues without output

B Jenkins fails the build immediately without showing test results

C Jenkins shows a summary of test results including passed, failed, and skipped tests

D Jenkins shows code coverage percentage instead of test results

💡 Hint

What does the junit step do with XML reports?

The junit step parses the XML test reports and displays a summary of test results in Jenkins, including counts of passed, failed, and skipped tests.

❓ assertion

advanced

Correct Assertion for JUnit Test Result in Jenkinsfile

Which assertion correctly fails the Jenkins build if any JUnit test fails?

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
        // Assertion here
      }
    }
  }
}

A script { if (currentBuild.result != 'SUCCESS') error('Tests failed') }

B script { assert currentBuild.result == 'SUCCESS' }

C script { if (currentBuild.result == 'FAILURE') error('Tests failed') }

D script { assert currentBuild.result != 'FAILURE' }

💡 Hint

Consider how Jenkins sets currentBuild.result after tests.

After the junit step, Jenkins sets currentBuild.result to 'UNSTABLE' if any test fails. The assertion should fail the build if the result is not 'SUCCESS'. Option A correctly checks this.

🔧 Debug

advanced

Debugging Missing JUnit Test Reports in Jenkins

After running tests, Jenkins shows 'No test reports found'. What is the most likely cause?

A The Jenkinsfile syntax is invalid causing the step to be skipped

B The tests did not run because the build agent was offline

C JUnit is not installed on the Jenkins server

D The path in the <code>junit</code> step does not match the actual location of XML files

💡 Hint

Check the file path pattern used in the junit step.

If the junit step path does not match where the XML reports are saved, Jenkins cannot find and display test results, causing the 'No test reports found' message.

❓ framework

expert

Configuring Jenkins to Archive JUnit Reports and Fail Build on Test Failures

Which Jenkins pipeline snippet correctly archives JUnit test reports and fails the build if any test fails?

A

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
        script {
          if (currentBuild.result != 'SUCCESS') {
            error('Tests failed')
          }
        }
      }
    }
  }
  post {
    always {
      archiveArtifacts 'target/surefire-reports/*.xml'
    }
  }
}

B

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
      }
    }
  }
  post {
    always {
      archiveArtifacts 'target/surefire-reports/*.xml'
      script {
        if (currentBuild.result == 'FAILURE') {
          error('Tests failed')
        }
      }
    }
  }
}

C

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
        archiveArtifacts 'target/surefire-reports/*.xml'
      }
    }
  }
  post {
    failure {
      error('Tests failed')
    }
  }
}

D

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        junit 'target/surefire-reports/*.xml'
      }
    }
  }
  post {
    always {
      archiveArtifacts 'target/surefire-reports/*.xml'
    }
    failure {
      error('Tests failed')
    }
  }
}

💡 Hint

Consider where to check the build result and where to archive artifacts.

Option A archives artifacts in the post always block and checks currentBuild.result immediately after the junit step to fail the build if tests fail. This ensures proper sequencing and build failure on test failures.