Running unit tests in pipeline in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline stage?

Consider this Jenkins pipeline snippet that runs unit tests using Maven:

stage('Test') {
  steps {
    sh 'mvn test'
  }
}

What will Jenkins display if the tests pass successfully?

Jenkins

stage('Test') {
  steps {
    sh 'mvn test'
  }
}

A Build succeeded with test results shown in console output

B Build failed due to test failures

C Build succeeded but no test results are shown

D Build skipped the test stage

💡 Hint

Think about what mvn test does and how Jenkins shows output.

The mvn test command runs unit tests and outputs results to the console. Jenkins shows this output in the build logs. If tests pass, the build succeeds and test results appear in the console.

❓ Configuration

intermediate

Which Jenkinsfile snippet correctly archives JUnit test results?

You want Jenkins to archive JUnit test reports after running tests. Which snippet correctly configures this?

A

steps {
  archiveArtifacts '**/target/surefire-reports/*.xml'
}

B

steps {
  junit '**/target/surefire-reports/*.xml'
}

C

post {
  success {
    junit '**/target/surefire-reports/*.xml'
  }
}

D

post {
  always {
    junit '**/target/surefire-reports/*.xml'
  }
}

💡 Hint

Archiving test results should happen regardless of build success or failure.

The post { always { junit(...) }} block ensures test results are archived no matter what. Option D archives artifacts but not test results. Option D archives test results but not in a post block. Option D archives only on success.

🔀 Workflow

advanced

Order the Jenkins pipeline steps to run unit tests and publish results correctly

Arrange these Jenkins pipeline steps in the correct order to run unit tests and publish their results:

A 2,3,1,4

B 3,1,2,4

C 3,2,1,4

D 1,3,2,4

💡 Hint

Think about the logical order: get code, run tests, archive results, then notify.

First, Jenkins must checkout the source code (3). Then it runs unit tests (1). After tests complete, it archives the test results (2). Finally, it notifies the build status (4).

❓ Troubleshoot

advanced

What error will occur if the test report path is incorrect in the Jenkinsfile?

Given this Jenkinsfile snippet:

post {
  always {
    junit '**/wrong-path/*.xml'
  }
}

What will Jenkins report after running tests?

Jenkins

post {
  always {
    junit '**/wrong-path/*.xml'
  }
}

A Build succeeds with no warnings

B Build fails with a syntax error

C No test reports found, build marked as unstable

D Build fails with a file not found exception

💡 Hint

Consider what happens if Jenkins cannot find any test report files.

If Jenkins cannot find any test report files matching the pattern, it marks the build as unstable and logs a warning. It does not fail the build or throw a syntax error.

✅ Best Practice

expert

Which Jenkins pipeline practice ensures reliable unit test execution in parallel stages?

You want to run unit tests in parallel stages for different modules. Which practice ensures tests run reliably without interfering with each other?

A Use separate workspace directories for each parallel stage

B Run all tests in a single stage sequentially

C Disable test result archiving to speed up the build

D Use the same workspace for all parallel stages to share files

💡 Hint

Think about file conflicts when running parallel jobs.

Using separate workspace directories for each parallel stage prevents file conflicts and ensures tests run independently. Sharing the same workspace can cause race conditions and test failures.