Failing builds on test failures in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What happens when a Jenkins pipeline stage runs tests that fail?

Consider a Jenkins pipeline with a test stage that runs unit tests using a shell command. If some tests fail, what will Jenkins do by default?

Jenkins

stage('Test') {
  steps {
    sh 'pytest tests/'
  }
}

A The build will fail and stop immediately after the test command returns a non-zero exit code.

B The build will continue to the next stage regardless of test failures.

C The build will mark the test stage as unstable but continue running other stages.

D The build will ignore test failures and mark the build as successful.

💡 Hint

Think about how shell commands signal failure in Jenkins pipelines.

By default, Jenkins treats any non-zero exit code from a shell command as a failure, causing the build to fail and stop.

❓ Configuration

intermediate

How to configure Jenkins to fail build on test failures using JUnit plugin?

You want Jenkins to run tests and fail the build if any test fails, using the JUnit plugin to parse test reports. Which post-build action configuration ensures this?

A Publish JUnit test result report with 'Mark build as unstable' option checked and no fail option.

B Do not publish JUnit reports; rely on shell exit codes only.

C Publish JUnit test result report with 'Fail the build if test results are unstable' option checked.

D Publish JUnit test result report without any fail or unstable options checked.

💡 Hint

Look for the option that causes build failure on test failures in the JUnit plugin settings.

Checking 'Fail the build if test results are unstable' causes Jenkins to mark the build as failed if any test fails.

❓ Troubleshoot

advanced

Why does Jenkins build succeed even though tests fail in a pipeline?

You have a Jenkins pipeline running tests with a shell command. Tests fail, but the build still shows success. What is the most likely cause?

Jenkins

stage('Test') {
  steps {
    sh(script: 'pytest tests/', returnStatus: true)
  }
}

A The tests actually passed, so the build is correct.

B The shell step uses 'returnStatus: true', so it returns the exit code but does not fail the build automatically.

C The Jenkins agent is offline, so the build status is not updated.

D The pipeline syntax is incorrect, causing Jenkins to ignore test failures.

💡 Hint

Check how the shell step handles exit codes with 'returnStatus'.

Using 'returnStatus: true' makes the shell step return the exit code instead of failing the build automatically. The pipeline must check the code to fail explicitly.

🔀 Workflow

advanced

How to fail a Jenkins pipeline build on test failures when using 'returnStatus' in shell step?

You run tests in a Jenkins pipeline using a shell step with 'returnStatus: true' to capture exit code. How do you fail the build if tests fail?

Jenkins

stage('Test') {
  steps {
    script {
      def status = sh(script: 'pytest tests/', returnStatus: true)
      // What to do here?
    }
  }
}

A Add 'echo "Tests failed"' without failing the build.

B Add 'return status' to propagate the exit code automatically.

C Add 'sh "exit $status"' to retry the tests.

D Add 'if (status != 0) { error("Tests failed") }' to explicitly fail the build.

💡 Hint

Think about how to make the pipeline fail explicitly based on a variable.

Using 'error()' in the pipeline script causes the build to fail immediately with a message.

✅ Best Practice

expert

Best practice to ensure Jenkins build fails on test failures and reports results clearly

Which approach best ensures Jenkins build fails on test failures and provides clear test reports in the UI?

A Run tests with shell step capturing exit code, then publish JUnit reports with 'Fail the build if test results are unstable' enabled.

B Run tests with shell step and rely on console output only, no JUnit reports.

C Run tests with shell step ignoring exit code, then only echo test results without publishing reports.

D Run tests with shell step and mark build unstable regardless of test results.

💡 Hint

Consider both failing the build and showing test results in Jenkins UI.

Capturing exit code ensures build fails on test failures; publishing JUnit reports with failure option shows detailed test results and fails build properly.