Why testing in pipelines matters in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a testing stage in a Jenkins pipeline.

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [1] 'run tests'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ainput

Barchive

Csh

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using input instead of sh to run tests.

The sh step runs shell commands, which is used here to run tests in the pipeline.

2fill in blank

medium

Complete the code to fail the pipeline if tests fail.

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [1] 'exit 1'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Aarchive

Becho

Cinput

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo which only prints text and does not fail the build.

The sh step runs shell commands. Using exit 1 causes the step to fail, which fails the pipeline.

3fill in blank

hard

Fix the error in the pipeline to properly run tests and fail on errors.

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [1] 'pytest || exit 1'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ainput

Bsh

Carchive

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using input which pauses the pipeline instead of running commands.

The sh step runs shell commands. Using pytest || exit 1 runs tests and fails the pipeline if tests fail.

4fill in blank

hard

Fill both blanks to add a test stage that runs tests and archives results.

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [1] 'run_tests.sh'
        [2] artifacts: 'test-results/*.xml', fingerprint: true
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ash

Binput

CarchiveArtifacts

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using input instead of sh to run tests.

The sh step runs the test script. The archiveArtifacts step saves test result files for later review.

5fill in blank

hard

Fill all three blanks to create a pipeline that checks out code, runs tests, and archives results.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build and Test') {
      steps {
        [1] scm
        [2] './run_tests.sh'
        [3] artifacts: 'results/*.xml', fingerprint: true
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Acheckout

Bsh

CarchiveArtifacts

Dinput

Attempts:

3 left

💡 Hint

Common Mistakes

Using input which pauses the pipeline instead of running commands.

checkout gets the code from source control, sh runs the test script, and archiveArtifacts saves the test results.