JUnit test report publishing in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

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

Publishing JUnit test reports in Jenkins helps to visualize test results, track test failures, and monitor test trends over time in a clear and organized way.

beginner

Which Jenkins plugin is commonly used to publish JUnit test reports?

The 'JUnit Plugin' is commonly used in Jenkins to publish and display JUnit test reports.

beginner

What file format does Jenkins expect for JUnit test reports?

Jenkins expects JUnit test reports in XML format, usually named with a pattern like '**/target/surefire-reports/*.xml'.

intermediate

How do you configure Jenkins to publish JUnit test reports after a build?

In the Jenkins job configuration, add a 'Post-build Action' called 'Publish JUnit test result report', then specify the path to the XML report files.

intermediate

What happens if Jenkins cannot find any JUnit XML report files during publishing?

If Jenkins cannot find the specified JUnit XML files, it will mark the test report publishing step as failed or unstable, and no test results will be shown.

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

A To write new test cases

B To speed up the build process

C To deploy the application automatically

D To see test results and failures clearly

Publishing JUnit test reports helps visualize test results and failures clearly in Jenkins.

Which file pattern is typically used to locate JUnit XML reports in Jenkins?

A **/target/surefire-reports/*.xml

B **/*.html

C **/build.log

D **/*.json

JUnit XML reports are usually found in the 'target/surefire-reports' directory with '*.xml' files.

Where do you add the JUnit test report publishing step in Jenkins job configuration?

A Build Environment

B Build Triggers

C Post-build Actions

D Source Code Management

JUnit test report publishing is added as a Post-build Action in Jenkins.

What plugin must be installed to publish JUnit test reports in Jenkins?

A JUnit Plugin

B Git Plugin

C Docker Plugin

D Slack Notification Plugin

The JUnit Plugin is required to publish JUnit test reports in Jenkins.

If Jenkins does not find any JUnit XML files, what is the likely result?

A Jenkins restarts

B Test report publishing fails or shows no results

C Build automatically passes

D Tests are rerun automatically

Without XML files, Jenkins cannot publish test results and may mark the step as failed or unstable.

Explain how to configure Jenkins to publish JUnit test reports after running tests.

Think about where in the Jenkins job settings you add steps after the build.

Describe what information Jenkins shows when JUnit test reports are published.

Consider what you want to see after running tests to understand their results.

Practice

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

easy

A. To run tests faster on Jenkins agents

B. To display test results clearly in Jenkins for easy review

C. To compile Java code before testing

D. To deploy the application automatically after tests

Solution

1. Step 1: Understand JUnit report publishing

   Publishing JUnit reports in Jenkins helps show test results in a readable format.

2. Step 2: Identify the main goal

   The main goal is to review test outcomes easily, not to run tests or deploy code.

3. Final Answer:

   To display test results clearly in Jenkins for easy review -> Option B

4. Quick Check:

   JUnit reports show test results [OK]

Hint: JUnit reports = test results display in Jenkins [OK]

Common Mistakes:

• Confusing report publishing with running tests
• Thinking it compiles code
• Assuming it triggers deployment

2. Which Jenkins pipeline syntax correctly publishes JUnit test reports stored in target/surefire-reports/*.xml?

easy

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

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

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

D. publishJUnit 'target/surefire-reports/*.xml'

Solution

1. Step 1: Identify correct placement of junit step

   The junit step must be inside a post block, usually with always to run after build.

2. Step 2: Check syntax correctness

   post { always { junit 'target/surefire-reports/*.xml' } } uses post { always { junit 'path' } } which is correct syntax for publishing reports.

3. Final Answer:

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

4. Quick Check:

   junit inside post always block [OK]

Hint: Put junit step inside post { always { ... } } [OK]

Common Mistakes:

• Placing junit directly under steps without post
• Using wrong step name like publishJUnit
• Omitting the always block inside post

3. Given this Jenkins pipeline snippet, what will happen after the build if the test reports are saved in build/test-results/*.xml?

post {
  always {
    junit 'build/test-results/*.xml'
  }
}

medium

A. JUnit reports will be ignored because path is incorrect

B. Tests will rerun automatically after the build

C. Build will fail if no test reports are found

D. JUnit test results will be published and visible in Jenkins UI

Solution

1. Step 1: Understand junit step behavior

   The junit step publishes test results from the given XML path after the build.

2. Step 2: Check the path and effect

   The path build/test-results/*.xml matches where reports are saved, so results will be published and shown.

3. Final Answer:

   JUnit test results will be published and visible in Jenkins UI -> Option D

4. Quick Check:

   Correct path + junit step = results published [OK]

Hint: Correct path in junit step shows results in Jenkins [OK]

Common Mistakes:

• Thinking tests rerun automatically
• Assuming build fails if reports missing
• Believing reports are ignored without error

4. You added this to your Jenkinsfile but test reports do not appear in Jenkins UI:

post {
  always {
    junit 'reports/*.xml'
  }
}

What is the most likely cause?

medium

A. The junit step must be inside the steps block, not post

B. The junit step requires a full absolute path

C. The report files are not saved in the 'reports' directory

D. The pipeline must use 'archiveArtifacts' to publish reports

Solution

1. Step 1: Verify report file location

   If reports are not saved in 'reports/*.xml', junit cannot find them to publish.

2. Step 2: Understand junit step requirements

   junit works with relative paths and does not require absolute paths or archiveArtifacts for publishing test results.

3. Final Answer:

   The report files are not saved in the 'reports' directory -> Option C

4. Quick Check:

   Wrong report path = no results shown [OK]

Hint: Check report file path matches junit pattern [OK]

Common Mistakes:

• Placing junit outside post block
• Using absolute paths unnecessarily
• Confusing junit with archiveArtifacts

5. You want Jenkins to publish JUnit reports only if tests run successfully, but still archive reports even if tests fail. Which Jenkinsfile snippet achieves this?

hard

A. post {
success {
junit 'test-results/*.xml'
}
always {
archiveArtifacts 'test-results/*.xml'
}
}

B. post {
always {
junit 'test-results/*.xml'
archiveArtifacts 'test-results/*.xml'
}
}

C. post {
failure {
junit 'test-results/*.xml'
}
success {
archiveArtifacts 'test-results/*.xml'
}
}

D. post {
success {
archiveArtifacts 'test-results/*.xml'
}
always {
junit 'test-results/*.xml'
}
}

Solution

1. Step 1: Understand conditions for junit and archiveArtifacts

   To publish JUnit reports only on success, place junit inside success block. To archive always, place archiveArtifacts inside always.

2. Step 2: Match snippet to requirements

   post { success { junit 'test-results/*.xml' } always { archiveArtifacts 'test-results/*.xml' } } correctly uses success { junit } and always { archiveArtifacts }, meeting the goal.

3. Final Answer:

   post { success { junit 'test-results/*.xml' } always { archiveArtifacts 'test-results/*.xml' } } -> Option A

4. Quick Check:

   junit on success + archive always [OK]

Hint: Use success for junit, always for archiveArtifacts [OK]

Common Mistakes:

• Putting junit in always block causing publish on failure
• Swapping archiveArtifacts and junit blocks
• Using failure block incorrectly