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.

Practice

1. What is the main purpose of running unit tests in a Jenkins pipeline?

easy

A. To monitor server performance

B. To deploy the application automatically

C. To create a backup of the code repository

D. To catch bugs early and ensure code quality

Solution

1. Step 1: Understand the role of unit tests

   Unit tests check small parts of code to find bugs early.

2. Step 2: Connect unit tests to pipeline goals

   Running tests in Jenkins pipeline helps maintain code quality before deployment.

3. Final Answer:

   To catch bugs early and ensure code quality -> Option D

4. Quick Check:

   Unit tests catch bugs early [OK]

Hint: Unit tests catch bugs early, not deploy or backup [OK]

Common Mistakes:

• Confusing testing with deployment
• Thinking tests create backups
• Assuming tests monitor performance

2. Which Jenkins pipeline syntax correctly runs unit tests using a shell command?

easy

A. execute shell('pytest tests/')

B. sh 'pytest tests/'

C. run 'pytest tests/'

D. command('pytest tests/')

Solution

1. Step 1: Recall Jenkins pipeline shell syntax

   Jenkins uses the sh step to run shell commands.

2. Step 2: Match the correct syntax

   sh 'pytest tests/' is the correct way to run tests in a shell step.

3. Final Answer:

   sh 'pytest tests/' -> Option B

4. Quick Check:

   Use sh for shell commands [OK]

Hint: Use 'sh' step to run shell commands in Jenkins pipeline [OK]

Common Mistakes:

• Using non-existent steps like 'run' or 'command'
• Incorrect function syntax for shell commands
• Missing quotes around command string

3. Given this Jenkins pipeline snippet, what will be the output if tests fail?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'pytest tests/'
      }
    }
  }
}

medium

A. Pipeline fails and stops execution

B. Pipeline ignores test failures and continues

C. Pipeline retries the test stage automatically

D. Pipeline marks tests as passed regardless

Solution

1. Step 1: Understand default behavior of sh step

   The sh step fails the pipeline if the command exits with a non-zero status (test failure).

2. Step 2: Predict pipeline reaction to test failure

   Since tests fail, the pipeline stage fails and stops further execution.

3. Final Answer:

   Pipeline fails and stops execution -> Option A

4. Quick Check:

   sh fails pipeline on error [OK]

Hint: Failed shell commands stop pipeline by default [OK]

Common Mistakes:

• Assuming pipeline continues despite test failure
• Thinking Jenkins retries failed stages automatically
• Believing tests pass regardless of results

4. You wrote this Jenkins pipeline stage to run tests:

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

But the pipeline fails with a syntax error. What is the problem?

medium

A. Incorrect stage name

B. Missing agent declaration

C. Missing quotes around the shell command

D. Using 'sh' outside steps block

Solution

1. Step 1: Check shell command syntax in Jenkins pipeline

   The sh step requires the command as a quoted string.

2. Step 2: Identify missing quotes causing syntax error

   Here, sh pytest tests/ lacks quotes around pytest tests/.

3. Final Answer:

   Missing quotes around the shell command -> Option C

4. Quick Check:

   Shell commands must be quoted in sh step [OK]

Hint: Always quote shell commands in sh step [OK]

Common Mistakes:

• Forgetting quotes around commands
• Confusing stage name with syntax error cause
• Ignoring required agent declaration elsewhere

5. How can you modify a Jenkins pipeline to run unit tests but continue the pipeline even if tests fail, while still marking the test stage as unstable?

hard

A. Use catchError(buildResult: 'UNSTABLE', stageResult: 'UNSTABLE') { sh 'pytest tests/' }

B. Use sh 'pytest tests/' || true without any catchError

C. Remove the test stage from the pipeline

D. Use sh 'pytest tests/' inside a timeout block

Solution

1. Step 1: Understand how to catch errors without failing pipeline

   The catchError step can catch failures and mark the build unstable instead of failing.

2. Step 2: Apply catchError with proper parameters

   Using catchError(buildResult: 'UNSTABLE', stageResult: 'UNSTABLE') around the test command allows continuation but marks stage unstable.

3. Final Answer:

   Use catchError(buildResult: 'UNSTABLE', stageResult: 'UNSTABLE') { sh 'pytest tests/' } -> Option A

4. Quick Check:

   Use catchError to continue on test failure [OK]

Hint: Wrap tests in catchError to continue but mark unstable [OK]

Common Mistakes:

• Using '|| true' hides failures without marking unstable
• Removing test stage skips testing
• Timeout does not handle test failures