Parallel test execution in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run two test stages in parallel in Jenkins pipeline.

Jenkins

pipeline {
  agent any
  stages {
    stage('Parallel Tests') {
      steps {
        parallel {
          test1: {
            echo 'Running Test 1'
          },
          test2: [1]
        }
      }
    }
  }
}

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

A{ echo 'Running Test 2' }

B[ echo 'Running Test 2' ]

C( echo 'Running Test 2' )

D< echo 'Running Test 2' >

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets [] or parentheses () instead of braces {} for parallel stages.

Forgetting to wrap the steps inside braces.

In Jenkins pipeline, parallel stages are defined as blocks with braces {}. So the correct syntax for the second parallel stage is { echo 'Running Test 2' }.

2fill in blank

medium

Complete the code to define parallel stages with names 'Unit Tests' and 'Integration Tests'.

Jenkins

parallel {
  [1]: {
    echo 'Running Unit Tests'
  },
  integrationTests: {
    echo 'Running Integration Tests'
  }
}

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

AunitTests

BUnitTests

Cunit_tests

Dunit-tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using dashes '-' in stage names which is invalid syntax.

Using uppercase letters at the start which may cause confusion.

Stage names in Jenkins pipeline should be valid Groovy identifiers without special characters or spaces. 'unitTests' is a valid camelCase identifier.

3fill in blank

hard

Fix the error in the parallel block by completing the missing keyword.

Jenkins

pipeline {
  agent any
  stages {
    stage('Tests') {
      steps {
        [1] {
          testA: {
            echo 'Test A'
          },
          testB: {
            echo 'Test B'
          }
        }
      }
    }
  }
}

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

Asteps

Bsequence

Cstages

Dparallel

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stages' or 'steps' instead of 'parallel' causes syntax errors.

Omitting the keyword entirely.

The keyword 'parallel' is required to run multiple branches at the same time in Jenkins pipeline.

4fill in blank

hard

Fill both blanks to create a parallel block with two test stages that each run a shell command.

Jenkins

parallel {
  testOne: {
    sh [1] 'echo Test One'
  },
  testTwo: {
    sh [2] 'echo Test Two'
  }
}

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

A"script"

B'script'

C"command"

D'command'

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes for the argument name causes errors.

Using 'command' instead of 'script' as the argument name.

The 'sh' step in Jenkins pipeline uses the 'script' argument as a string to run shell commands. Double quotes are preferred for Groovy strings.

5fill in blank

hard

Fill all three blanks to define a parallel block with three test stages, each echoing a different message.

Jenkins

parallel {
  testA: {
    echo [1]
  },
  testB: {
    echo [2]
  },
  testC: {
    echo [3]
  }
}

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

A'Running Test A'

B'Running Test B'

C'Running Test C'

D'Running Test D'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the messages between stages.

Forgetting to use quotes around the echo messages.

Each parallel stage should echo its own message. The correct messages are 'Running Test A', 'Running Test B', and 'Running Test C'.

Practice

1. What is the main purpose of using the parallel block in a Jenkins pipeline?

easy

A. To stop the pipeline if any test fails

B. To run multiple test groups at the same time to save time

C. To run tests one after another in a sequence

D. To deploy the application automatically after tests

Solution

1. Step 1: Understand the parallel block function

   The parallel block in Jenkins allows running multiple tasks simultaneously.

2. Step 2: Identify the benefit of parallel execution

   Running tests in parallel saves time by executing multiple test groups at once instead of sequentially.

3. Final Answer:

   To run multiple test groups at the same time to save time -> Option B

4. Quick Check:

   Parallel execution = run tests simultaneously [OK]

Hint: Parallel means running tasks at the same time [OK]

Common Mistakes:

• Thinking parallel runs tests one by one
• Confusing parallel with deployment steps
• Assuming parallel stops on first failure

2. Which of the following is the correct syntax to run two test stages in parallel in a Jenkins declarative pipeline?

easy

A. parallel {
stage('Test1') { steps { echo 'Run Test1' } }
stage('Test2') { steps { echo 'Run Test2' } }
}

B. parallel(
Test1: { stage('Test1') { steps { echo 'Run Test1' } } },
Test2: { stage('Test2') { steps { echo 'Run Test2' } } }
)

C. parallel(
Test1: { echo 'Run Test1' },
Test2: { echo 'Run Test2' }
)

D. parallel(
Test1: { steps { echo 'Run Test1' } },
Test2: { steps { echo 'Run Test2' } }
)

Solution

1. Step 1: Recall Jenkins parallel syntax

   In declarative pipelines, parallel takes a map of closures using scripted syntax with direct steps like echo.

2. Step 2: Check which option uses correct closure with direct steps

   parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) correctly uses parallel with keys and closures containing direct echo.

3. Final Answer:

   parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) -> Option C

4. Quick Check:

   parallel map with direct echo closures = parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) [OK]

Hint: parallel needs map keys with closures containing direct steps like echo [OK]

Common Mistakes:

• Using stage inside parallel directly (wrong in scripted)
• Adding steps block inside closures (declarative syntax mismatch)
• Using braces incorrectly for parallel syntax

3. Given the following Jenkins scripted pipeline snippet, what will be the output?

parallel(
  TestA: {
    echo 'Running Test A'
  },
  TestB: {
    echo 'Running Test B'
  }
)
echo 'All tests done'

medium

A. Running Test A\nRunning Test B\nAll tests done

B. Running Test A\nAll tests done\nRunning Test B

C. All tests done\nRunning Test A\nRunning Test B

D. Running Test B\nRunning Test A\nAll tests done

Solution

1. Step 1: Understand parallel execution output order

   Both TestA and TestB run at the same time, so their echo outputs appear before the next command.

2. Step 2: Identify the sequence of echo commands

   After both parallel tasks finish, the final echo 'All tests done' runs.

3. Final Answer:

   Running Test A\nRunning Test B\nAll tests done -> Option A

4. Quick Check:

   Parallel tests output first, then final echo [OK]

Hint: Parallel echoes appear before next sequential echo [OK]

Common Mistakes:

• Assuming output order is strictly sequential
• Thinking 'All tests done' prints before tests
• Confusing parallel output interleaving

4. You wrote this Jenkins pipeline snippet to run tests in parallel but it fails with a syntax error:

parallel(
  Test1: {
    stage('Test1') {
      steps {
        echo 'Running Test1'
      }
    }
  },
  Test2: {
    stage('Test2') {
      steps {
        echo 'Running Test2'
      }
    }
  }
)

What is the main cause of the error?

medium

A. Using parallel block outside a node block

B. Missing commas between parallel map entries

C. Incorrect indentation of the echo commands

D. Using stage and steps inside scripted pipeline closures

Solution

1. Step 1: Identify pipeline type and syntax rules

   In scripted pipelines, stage and steps blocks are not used inside closures passed to parallel.

2. Step 2: Recognize correct scripted pipeline parallel syntax

   Scripted pipelines use simple closures with commands like echo directly, without stage or steps.

3. Final Answer:

   Using stage and steps inside scripted pipeline closures -> Option D

4. Quick Check:

   Scripted parallel closures exclude stage/steps blocks [OK]

Hint: Scripted parallel closures don't use stage or steps blocks [OK]

Common Mistakes:

• Mixing declarative syntax inside scripted pipeline
• Forgetting commas between map entries (not the main error here)
• Assuming indentation causes syntax errors

5. You want to run three test suites in parallel in a Jenkins declarative pipeline and fail the entire build if any test fails. Which snippet correctly achieves this?

hard

A. stages {
stage('Parallel Tests') {
parallel {
Test1: { steps { sh 'run_test1.sh' } }
Test2: { steps { sh 'run_test2.sh' } }
Test3: { steps { sh 'run_test3.sh' } }
}
}
}

B. parallel {
stage('Test1') { steps { sh 'run_test1.sh' } }
stage('Test2') { steps { sh 'run_test2.sh' } }
stage('Test3') { steps { sh 'run_test3.sh' } }
}

C. stages {
parallel {
stage('Test1') { steps { sh 'run_test1.sh' } }
stage('Test2') { steps { sh 'run_test2.sh' } }
stage('Test3') { steps { sh 'run_test3.sh' } }
}
}

D. stage('Parallel Tests') {
parallel(
Test1: { sh 'run_test1.sh' },
Test2: { sh 'run_test2.sh' },
Test3: { sh 'run_test3.sh' }
)
}

Solution

1. Step 1: Recall declarative pipeline structure for parallel stages

   Declarative pipelines require a stages block containing stage blocks; parallel tests go inside a single stage with a parallel block.

2. Step 2: Identify correct syntax for parallel tests with failure propagation

   stages { stage('Parallel Tests') { parallel { Test1: { steps { sh 'run_test1.sh' } } Test2: { steps { sh 'run_test2.sh' } } Test3: { steps { sh 'run_test3.sh' } } } } } correctly uses stages block with a stage named 'Parallel Tests' containing a parallel block where each parallel branch is a closure with steps and sh commands. This is the proper declarative syntax and ensures the build fails if any test fails.

3. Final Answer:

   stages { stage('Parallel Tests') { parallel { Test1: { steps { sh 'run_test1.sh' } } Test2: { steps { sh 'run_test2.sh' } } Test3: { steps { sh 'run_test3.sh' } } } } } -> Option A

4. Quick Check:

   Declarative parallel inside a stage within stages block with steps closures [OK]

Hint: Use parallel inside a stage within stages block with steps closures [OK]

Common Mistakes:

• Placing parallel outside stages block
• Using parallel without wrapping in a stage
• Mixing scripted and declarative syntax