Test result trends in Jenkins - Commands & Configuration

Introduction

When you run tests in Jenkins, you want to see how your test results change over time. Test result trends help you spot if tests are getting better or worse. This helps keep your software healthy and reliable.

When you want to track if new code breaks existing tests over several builds

When you want to see if test failures are increasing or decreasing over time

When you want to quickly find builds with the most test failures

When you want to share test quality reports with your team automatically

When you want to improve your testing process by analyzing test trends

Commands

This command creates or updates a Jenkins job from a YAML file that includes test reporting configuration. It sets up the job to run tests and collect results.

Terminal

jenkins-jobs --conf jenkins.ini test-job.yaml

Expected Output

Job 'test-job' created or updated successfully

→

--conf - Specifies the Jenkins server configuration file

This command triggers the Jenkins job named 'test-job' and waits for it to finish. It runs the tests and collects the results.

Terminal

jenkins-cli build test-job -s

Expected Output

Started build #1

Finished: SUCCESS

→

-s - Waits for the build to complete before returning

This command shows the console output of build number 1 of the 'test-job'. You can check test execution details here.

Terminal

jenkins-cli console test-job 1

Expected Output

[Pipeline] Start of Pipeline

Running tests...

Tests passed: 10, failed: 0

[Pipeline] End of Pipeline

Finished: SUCCESS

This command retrieves the job configuration XML. You can verify that the test reporting plugin is configured to collect test results for trend analysis.

Terminal

jenkins-cli get-job test-job

Expected Output

<?xml version="1.0" encoding="UTF-8"?>

<project>

  <publishers>

    <hudson.tasks.junit.JUnitResultArchiver>

      <testResults>**/test-results.xml</testResults>

      <keepLongStdio>false</keepLongStdio>

      <healthScaleFactor>1.0</healthScaleFactor>

    </hudson.tasks.junit.JUnitResultArchiver>

  </publishers>

</project>

Key Concept

If you remember nothing else from this pattern, remember: Jenkins collects test results each build and shows trends over time to help you track test health.

Common Mistakes

Not configuring the test result archiver plugin in the Jenkins job

Without this, Jenkins won't collect test results and cannot show trends.

Add the JUnit test result archiver step in the job configuration pointing to the test result files.

Running tests but not publishing the test result files

Jenkins needs the test result files to generate trend reports; missing files mean no data.

Ensure your test runner outputs test results in a format Jenkins understands and that the job archives these files.

Triggering builds without waiting for completion before checking results

You might check results before tests finish, leading to incomplete or missing data.

Use flags or commands that wait for the build to finish before accessing test results.

Summary

Create or update a Jenkins job configured to run tests and archive test results.

Trigger the Jenkins job and wait for it to complete to ensure test results are collected.

View the console output and job configuration to verify tests ran and results are archived.

Jenkins uses archived test results to show test result trends over multiple builds.

Practice

1. What is the main purpose of test result trends in Jenkins?

easy

A. To show how test results change over time

B. To run tests faster

C. To deploy applications automatically

D. To create new test cases

Solution

1. Step 1: Understand test result trends concept

   Test result trends track test outcomes across multiple builds to see progress or issues.

2. Step 2: Identify the main purpose

   The main goal is to observe changes in test results over time, helping catch problems early.

3. Final Answer:

   To show how test results change over time -> Option A

4. Quick Check:

   Test result trends = show changes over time [OK]

Hint: Trends track test results over builds, not speed or deployment [OK]

Common Mistakes:

• Confusing trends with deployment automation
• Thinking trends create tests
• Assuming trends speed up tests

2. Which Jenkins plugin is required to publish test result trends from JUnit XML reports?

easy

A. Git plugin

B. Docker plugin

C. Pipeline plugin

D. JUnit plugin

Solution

1. Step 1: Identify plugin for JUnit XML reports

   JUnit plugin in Jenkins processes JUnit XML test reports and generates test result trends.

2. Step 2: Confirm plugin role

   Only the JUnit plugin handles test result publishing and trend visualization from JUnit reports.

3. Final Answer:

   JUnit plugin -> Option D

4. Quick Check:

   JUnit plugin publishes test trends [OK]

Hint: JUnit plugin handles JUnit XML test reports and trends [OK]

Common Mistakes:

• Choosing Git plugin which manages source code
• Selecting Docker plugin unrelated to tests
• Confusing Pipeline plugin with test reporting

3. Given this Jenkins pipeline snippet, what will happen if the junit '**/test-results.xml' step is missing?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'run-tests.sh'
        junit '**/test-results.xml'
      }
    }
  }
}

medium

A. Test results will be published and trends shown

B. No test results will be published, no trends available

C. Pipeline will fail with syntax error

D. Tests will not run at all

Solution

1. Step 1: Understand the role of junit step

   The junit step publishes test results from XML files and enables trend graphs.

2. Step 2: Analyze missing junit step effect

   Without junit, test results are not published, so no trends appear, but tests still run.

3. Final Answer:

   No test results will be published, no trends available -> Option B

4. Quick Check:

   Missing junit step = no published results [OK]

Hint: Without junit step, no test results or trends appear [OK]

Common Mistakes:

• Thinking pipeline fails without junit step
• Assuming tests won't run without junit
• Believing trends show without publishing results

4. You added the junit '**/results.xml' step but Jenkins shows no test trends. What is the most likely cause?

medium

A. The XML file path pattern is incorrect or no files match

B. The Jenkins server is offline

C. The pipeline syntax is invalid

D. The tests did not run

Solution

1. Step 1: Check file path pattern for test reports

   If the pattern **/results.xml does not match any files, no results are published.

2. Step 2: Confirm Jenkins behavior on missing files

   Jenkins silently skips publishing if no matching files found, so no trends appear.

3. Final Answer:

   The XML file path pattern is incorrect or no files match -> Option A

4. Quick Check:

   Wrong file path = no test trends [OK]

Hint: Verify XML file path matches actual test report location [OK]

Common Mistakes:

• Assuming Jenkins is offline without checking
• Blaming pipeline syntax without error
• Thinking tests must fail to hide trends

5. You want to track test result trends for multiple test suites in Jenkins, each producing separate JUnit XML files in different folders. How should you configure the junit step to show combined trends?

hard

A. Manually merge XML files before publishing

B. Use multiple junit steps, one per folder

C. Use a single junit step with a combined glob pattern like '**/test-results/*.xml'

D. Publish only one folder's results to avoid confusion

Solution

1. Step 1: Understand how junit step handles multiple files

   The junit step accepts glob patterns to include multiple XML files from different folders.

2. Step 2: Choose best practice for combined trends

   Using a single junit step with a combined pattern like '**/test-results/*.xml' publishes all results together, enabling combined trends.

3. Final Answer:

   Use a single junit step with a combined glob pattern like '**/test-results/*.xml' -> Option C

4. Quick Check:

   Single junit step + combined pattern = combined trends [OK]

Hint: Use one junit step with glob pattern to include all XML files [OK]

Common Mistakes:

• Using multiple junit steps causing separate trends
• Trying to merge XML files manually
• Ignoring some test suites results