Jenkins pipeline integration in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage named 'Build'.

Selenium Java

stage('[1]') {
    steps {
        echo 'Building the project'
    }
}

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

ATest

BDeploy

CBuild

DClean

Attempts:

3 left

💡 Hint

Common Mistakes

Using a stage name that does not match the build process.

Forgetting to put the stage name in quotes.

The stage block defines a pipeline stage. Here, the stage is named 'Build' to represent the build step.

2fill in blank

medium

Complete the code to run a shell command in the Jenkins pipeline.

Selenium Java

steps {
    [1] 'mvn clean install'
}

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

Ash

Bbat

Cpowershell

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using bat on Linux agents causing errors.

Forgetting to use a step to run shell commands.

The sh step runs shell commands on Unix/Linux agents. Here, it runs the Maven build command.

3fill in blank

hard

Fix the error in the Jenkins pipeline syntax to declare an agent.

Selenium Java

pipeline {
    agent {
        [1] 'linux'
    }
    stages {
        stage('Test') {
            steps {
                echo 'Running tests'
            }
        }
    }
}

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

Anode

Bnone

Cany

Dlabel

Attempts:

3 left

💡 Hint

Common Mistakes

Using any without braces causes syntax errors here.

Confusing node with agent syntax.

The agent { label 'linux' } block specifies the pipeline runs on agents labeled 'linux'.

4fill in blank

hard

Fill both blanks to define a post-build action that always runs and sends a notification.

Selenium Java

post {
    [1] {
        [2] 'Build completed'
    }
}

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

Aalways

Bsuccess

Cecho

Dfailure

Attempts:

3 left

💡 Hint

Common Mistakes

Using success instead of always to run post actions.

Using sh instead of echo for simple messages.

The always block runs regardless of build result. The echo step prints a message.

5fill in blank

hard

Fill all three blanks to create a parallel stage with two branches named 'UI Tests' and 'API Tests'.

Selenium Java

stage('Test') {
    parallel {
        '[1]': {
            steps {
                [2] 'Running UI tests'
            }
        },
        '[3]': {
            steps {
                echo 'Running API tests'
            }
        }
    }
}

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

AUI Tests

Becho

CAPI Tests

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using sh instead of echo for simple messages.

Mixing up branch names or missing quotes.

The parallel block runs multiple branches at the same time. Branch names are 'UI Tests' and 'API Tests'. The echo step prints messages.

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