CI pipeline test stage in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a JUnit test run in CI pipeline

What is the output of this JUnit test run command in a CI pipeline when all tests pass?

JUnit

mvn test

A [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0

B [WARNING] Tests run: 10, Failures: 0, Errors: 1, Skipped: 0

C [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 0

D [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 2

💡 Hint

Look for zero failures and errors in the test summary.

When all tests pass, the summary shows zero failures, zero errors, and zero skipped tests.

❓ Configuration

intermediate

JUnit test stage configuration in Jenkinsfile

Which Jenkinsfile snippet correctly defines a test stage that runs JUnit tests and archives the results?

A

stage('Test') {
  steps {
    sh 'mvn test'
    junit '**/target/surefire-reports/*.xml'
  }
}

B

stage('Test') {
  steps {
    sh 'mvn compile'
    junit '**/target/surefire-reports/*.xml'
  }
}

C

stage('Test') {
  steps {
    sh 'mvn test'
    archiveArtifacts '**/target/surefire-reports/*.xml'
  }
}

D

stage('Test') {
  steps {
    sh 'mvn test'
    junit '**/target/junit-reports/*.xml'
  }
}

💡 Hint

JUnit plugin expects test report XML files in surefire-reports directory.

The correct Jenkinsfile stage runs 'mvn test' and uses 'junit' step to archive reports from the surefire-reports folder.

❓ Troubleshoot

advanced

Diagnosing JUnit test failures in CI pipeline

A CI pipeline test stage running JUnit tests fails with this error: "No tests found". What is the most likely cause?

A The test reports are archived before tests run.

B The JUnit plugin is not installed in the CI server.

C The source code has compilation errors preventing tests from running.

D The test classes are not named according to the pattern recognized by the test runner.

💡 Hint

JUnit looks for test classes with specific naming conventions.

JUnit requires test classes to follow naming patterns like *Test.java to detect and run them.

🔀 Workflow

advanced

Correct order of steps in a CI pipeline test stage

What is the correct order of steps in a CI pipeline test stage using JUnit?

A 1,3,2,4

B 1,4,2,3

C 2,1,3,4

D 1,2,3,4

💡 Hint

Tests must run and fail the build before archiving and publishing results.

First run tests, then fail build if tests fail, then archive reports, then publish results.

✅ Best Practice

expert

Best practice for handling flaky JUnit tests in CI pipeline

Which approach is best to handle flaky JUnit tests in a CI pipeline test stage?

A Run flaky tests only locally and never in the CI pipeline

B Ignore test failures and always mark the build as successful

C Automatically retry failed tests a limited number of times before marking the build failed

D Remove flaky tests from the test suite permanently

💡 Hint

Flaky tests should be retried to reduce false negatives but not ignored.

Retrying flaky tests helps reduce false failures while keeping test quality and build reliability.