Jenkins pipeline integration in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline: Output of a simple stage

What will be the output in the Jenkins console log after running this pipeline snippet?

Selenium Java

pipeline {
  agent any
  stages {
    stage('Hello') {
      steps {
        echo 'Hello, Jenkins!'
      }
    }
  }
}

A Error: Missing agent declaration

B Hello, Jenkins!

C

pipeline {
  agent any
  stages {
    stage('Hello') {
      steps {
        echo 'Hello, Jenkins!'
      }
    }
  }
}

D No output

💡 Hint

Look at what the echo step does inside a stage.

The echo step prints the given message to the Jenkins console log during the pipeline execution.

🔀 Workflow

intermediate

Jenkins Pipeline: Parallel stages execution

Given this Jenkins pipeline snippet, which stages run in parallel?

Selenium Java

pipeline {
  agent any
  stages {
    stage('Build and Test') {
      parallel {
        stage('Build') {
          steps {
            echo 'Building...'
          }
        }
        stage('Test') {
          steps {
            echo 'Testing...'
          }
        }
      }
    }
  }
}

A Build and Test run in parallel inside the 'Build and Test' stage

B Build and Test stages run in parallel

C Only Build stage runs, Test stage is skipped

D Build and Test stages run sequentially

💡 Hint

Look at the 'parallel' block inside the 'Build and Test' stage.

The 'Build' and 'Test' stages are nested inside the 'Build and Test' stage and run in parallel as defined by the 'parallel' block.

❓ Configuration

advanced

Jenkins Pipeline: Correct syntax for environment variables

Which option correctly sets environment variables in a Jenkins declarative pipeline?

Selenium Java

pipeline {
  agent any
  environment {
    JAVA_HOME = '/usr/lib/jvm/java-11-openjdk'
    PATH = "$JAVA_HOME/bin:$PATH"
  }
  stages {
    stage('Print Env') {
      steps {
        sh 'echo $JAVA_HOME'
      }
    }
  }
}

A

environment {
  JAVA_HOME = '/usr/lib/jvm/java-11-openjdk'
  PATH = "$JAVA_HOME/bin:$PATH"
}

B

environment {
  JAVA_HOME: '/usr/lib/jvm/java-11-openjdk'
  PATH: "$JAVA_HOME/bin:$PATH"
}

C

environment {
  JAVA_HOME '/usr/lib/jvm/java-11-openjdk'
  PATH "$JAVA_HOME/bin:$PATH"
}

D

environment {
  JAVA_HOME => '/usr/lib/jvm/java-11-openjdk'
  PATH => "$JAVA_HOME/bin:$PATH"
}

💡 Hint

Check the syntax for environment variable assignment in Jenkins declarative pipelines.

In Jenkins declarative pipelines, environment variables are assigned using '=' inside the environment block.

❓ Troubleshoot

advanced

Jenkins Pipeline: Diagnosing a failed stage due to missing agent

A Jenkins pipeline stage fails with the error: 'No agent found for stage'. Which option explains the cause?

Selenium Java

pipeline {
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

A The stages block must be inside the steps block

B The echo step is invalid and causes the failure

C The pipeline is missing a global or stage-level agent declaration

D The pipeline syntax requires a tools block to run

💡 Hint

Every pipeline or stage needs an agent to run on.

Jenkins requires an agent declaration either globally or per stage to allocate an executor for running steps.

✅ Best Practice

expert

Jenkins Pipeline: Best practice for integrating Selenium Java tests

Which Jenkins pipeline snippet best integrates running Selenium Java tests with Maven and archives test reports?

A

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean compile'
        junit '**/target/surefire-reports/*.xml'
      }
    }
  }
}

B

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'java -jar selenium-tests.jar'
        archiveArtifacts '**/target/surefire-reports/*.xml'
      }
    }
  }
}

C

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
        archiveArtifacts '**/target/surefire-reports/*.xml'
      }
    }
  }
}

D

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
        junit '**/target/surefire-reports/*.xml'
      }
    }
  }
}

💡 Hint

Consider running tests and publishing test results properly.

Option D runs Maven tests and publishes test results with the junit step, which is the recommended way to integrate Selenium Java tests in Jenkins.

Practice

1. What is the main purpose of integrating Selenium Java tests into a Jenkins pipeline?

easy

A. To automate running tests and catch issues early

B. To manually trigger tests only when needed

C. To write Selenium tests inside Jenkins scripts

D. To replace Selenium with Jenkins for testing

Solution

1. Step 1: Understand Jenkins pipeline role

   Jenkins pipelines automate tasks like building and testing software continuously.

2. Step 2: Identify Selenium test integration benefit

   Integrating Selenium tests in Jenkins runs tests automatically to find problems early.

3. Final Answer:

   To automate running tests and catch issues early -> Option A

4. Quick Check:

   Automation + early detection = A [OK]

Hint: Jenkins pipelines run tests automatically to find bugs early [OK]

Common Mistakes:

• Thinking Jenkins replaces Selenium tests
• Believing tests run only manually
• Confusing Jenkins with test writing tool

2. Which Jenkinsfile syntax correctly defines a stage named 'Test' that runs Selenium tests using Maven?

easy

A. stage: 'Test' { steps: { sh 'mvn test' } }

B. stage('Test') steps { sh 'mvn test' }

C. stage('Test') { steps { sh 'mvn test' } }

D. stage('Test') { run 'mvn test' }

Solution

1. Step 1: Recall Jenkins declarative syntax

   Stages use the format stage('name') { steps { ... } } to define actions.

2. Step 2: Check each option's syntax

   stage('Test') { steps { sh 'mvn test' } } matches correct syntax; others have wrong punctuation or keywords.

3. Final Answer:

   stage('Test') { steps { sh 'mvn test' } } -> Option C

4. Quick Check:

   Correct stage block syntax = B [OK]

Hint: Use stage('name') { steps { ... } } for Jenkins pipeline stages [OK]

Common Mistakes:

• Using colons instead of braces
• Omitting steps block
• Using 'run' instead of 'sh' for shell commands

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

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean compile'
      }
    }
    stage('Test') {
      steps {
        sh 'mvn test'
      }
    }
  }
}

medium

A. Pipeline continues to next stage ignoring test failure

B. Pipeline stops and marks build as failed

C. Pipeline retries the test stage automatically

D. Pipeline marks build as successful despite failure

Solution

1. Step 1: Understand default Jenkins pipeline behavior

   By default, if a shell command fails (non-zero exit), Jenkins stops and marks build failed.

2. Step 2: Apply this to Maven test failure

   Since 'mvn test' fails, the pipeline stops and build is marked failed.

3. Final Answer:

   Pipeline stops and marks build as failed -> Option B

4. Quick Check:

   Failing shell command stops pipeline = A [OK]

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

Common Mistakes:

• Assuming pipeline continues after failure
• Thinking Jenkins retries automatically
• Believing build is marked successful on failure

4. You wrote this Jenkins pipeline snippet but tests never run:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean compile'
      }
    }
    stage('Test') {
      sh 'mvn test'
    }
  }
}

What is the error?

medium

A. Missing steps block inside 'Test' stage

B. Wrong agent declaration

C. Maven command syntax is incorrect

D. Pipeline missing post section

Solution

1. Step 1: Check 'Test' stage structure

   Each stage must have a steps block wrapping commands; 'Test' stage lacks it.

2. Step 2: Identify impact of missing steps block

   Without steps block, Jenkins ignores commands inside the stage, so tests don't run.

3. Final Answer:

   Missing steps block inside 'Test' stage -> Option A

4. Quick Check:

   Every stage needs steps block = C [OK]

Hint: Always wrap commands inside steps { } in Jenkins stages [OK]

Common Mistakes:

• Omitting steps block in stages
• Confusing agent syntax
• Thinking post section runs tests

5. How can you modify a Jenkins pipeline to run Selenium Java tests only if the build stage succeeds, and always archive test reports regardless of test results?

hard

A. Use 'when' condition to skip archiving if tests fail

B. Run tests in parallel with build stage and archive in 'failure' block

C. Skip build stage and run tests directly, archive in 'success' block

D. Use 'post' block with 'always' to archive reports and normal stages for build and test

Solution

1. Step 1: Ensure test stage runs after successful build

   By default, stages run sequentially; test stage runs only if build succeeds.

2. Step 2: Use 'post' block with 'always' to archive reports

   The 'post' block with 'always' runs regardless of test success or failure, ensuring reports are archived.

3. Final Answer:

   Use 'post' block with 'always' to archive reports and normal stages for build and test -> Option D

4. Quick Check:

   Sequential stages + post always archive = D [OK]

Hint: Use post { always { ... } } to archive reports every run [OK]

Common Mistakes:

• Running tests in parallel with build
• Archiving only on success or failure
• Skipping build stage before tests