Jenkins integration in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins CLI command output

What is the output of this Jenkins CLI command when listing all jobs in a Jenkins instance with two jobs named 'BuildApp' and 'TestApp'?

Selenium Python

java -jar jenkins-cli.jar -s http://localhost:8080/ list-jobs

A ERROR: No such command 'list-jobs'

B

BuildApp
TestApp

C BuildApp TestApp

D No jobs found

💡 Hint

The list-jobs command outputs job names separated by new lines.

The list-jobs command lists all job names line by line. So the output will be the job names separated by new lines.

❓ Configuration

intermediate

Jenkins Pipeline to run Selenium tests

Which Jenkinsfile snippet correctly defines a pipeline stage to run Selenium Python tests using a virtual environment?

A

stage('Test') {
  steps {
    sh 'python3 -m venv venv'
    sh './venv/bin/pip install -r requirements.txt'
    sh './venv/bin/python -m unittest discover tests'
  }
}

B

stage('Test') {
  steps {
    sh 'pip install -r requirements.txt'
    sh 'python -m unittest discover tests'
  }
}

C

stage('Test') {
  steps {
    sh 'python3 -m venv venv'
    sh 'pip install -r requirements.txt'
    sh 'python -m unittest discover tests'
  }
}

D

stage('Test') {
  steps {
    sh 'virtualenv venv'
    sh './venv/bin/pip install -r requirements.txt'
    sh 'python -m unittest discover tests'
  }
}

💡 Hint

The virtual environment's pip and python executables must be used explicitly.

Option A correctly creates a virtual environment, installs dependencies inside it, and runs tests using the virtual environment's python executable.

❓ Troubleshoot

advanced

Jenkins Selenium test failure due to missing display

A Jenkins job running Selenium tests on a Linux server fails with the error 'selenium.common.exceptions.WebDriverException: Message: unknown error: cannot find X display'. What is the most likely cause?

A The Jenkins user does not have permission to access the display server.

B The Selenium WebDriver version is incompatible with the browser version.

C The Python virtual environment is missing required packages.

D There is no graphical display (X server) available on the Linux server.

💡 Hint

Selenium needs a graphical environment to run browser tests unless using headless mode.

The error indicates Selenium cannot find a graphical display. On headless Linux servers, an X server or virtual display like Xvfb is needed.

🔀 Workflow

advanced

Jenkins pipeline steps for Selenium test automation

In a Jenkins pipeline for Selenium Python tests, which sequence of steps is the correct order to ensure tests run successfully?

A 2,1,3,4

B 3,1,2,4

C 1,2,3,4

D 1,3,2,4

💡 Hint

You must have the code before setting up environment and installing dependencies.

First, Jenkins checks out the code, then sets up the environment, installs dependencies, and finally runs tests.

✅ Best Practice

expert

Best practice for Jenkins Selenium test reports

Which Jenkins configuration is best to collect and display Selenium Python unittest XML test reports after a pipeline run?

A Use the 'Publish JUnit test result report' post-build action with the path to XML files generated by unittest.

B Send the XML files via email to the team without storing them in Jenkins.

C Archive the XML files as build artifacts without any test report plugin.

D Convert XML reports to HTML manually and archive the HTML files.

💡 Hint

Jenkins has built-in support for JUnit XML reports to visualize test results.

Option A uses Jenkins' native JUnit report publisher to parse and display test results in the UI, which is the best practice.

Practice

1. What is the main purpose of integrating Selenium Python tests with Jenkins?

easy

A. To write Selenium test scripts faster

B. To automate running tests and get quick feedback

C. To manually run tests on different browsers

D. To replace Selenium with Jenkins for testing

Solution

1. Step 1: Understand Jenkins role

   Jenkins automates tasks like running tests without manual effort.

2. Step 2: Connect Selenium tests with Jenkins

   Integrating Selenium tests with Jenkins allows automatic test execution and quick feedback on code changes.

3. Final Answer:

   To automate running tests and get quick feedback -> Option B

4. Quick Check:

   Automation + feedback = A [OK]

Hint: Jenkins automates tasks, so pick automation-related answer [OK]

Common Mistakes:

• Thinking Jenkins replaces Selenium
• Assuming Jenkins only helps write tests
• Confusing manual and automated test runs

2. Which Jenkins Pipeline step correctly runs a Selenium Python test script named test_login.py?

easy

A. run 'test_login.py'

B. execute python test_login.py

C. sh 'python3 test_login.py'

D. bash python3 test_login.py

Solution

1. Step 1: Identify correct Jenkins syntax

   Jenkins Pipeline uses sh step to run shell commands.

2. Step 2: Check command correctness

   python3 test_login.py is the correct shell command to run the Python script.

3. Final Answer:

   sh 'python3 test_login.py' -> Option C

4. Quick Check:

   Jenkins shell step = sh 'command' [OK]

Hint: Jenkins shell commands use sh 'command' syntax [OK]

Common Mistakes:

• Using invalid Jenkins step names like run or execute
• Missing quotes around shell command
• Confusing bash keyword with Jenkins syntax

3. Given this Jenkins Pipeline snippet, what will be the output if test_login.py fails?

pipeline {
  agent any
  stages {
    stage('Run Tests') {
      steps {
        sh 'python3 test_login.py'
      }
    }
  }
}

medium

A. Jenkins marks the build as failed and stops the pipeline

B. Jenkins ignores the failure and continues the pipeline

C. Jenkins retries the test automatically

D. Jenkins marks the build as successful regardless

Solution

1. Step 1: Understand Jenkins shell step behavior

   If the shell command exits with a non-zero code (test fails), Jenkins marks the build as failed.

2. Step 2: Pipeline stops on failure by default

   Without special handling, Jenkins stops the pipeline on failure and marks build failed.

3. Final Answer:

   Jenkins marks the build as failed and stops the pipeline -> Option A

4. Quick Check:

   Shell failure = build fail + stop [OK]

Hint: Shell command failure stops Jenkins pipeline by default [OK]

Common Mistakes:

• Assuming Jenkins retries tests automatically
• Thinking Jenkins ignores failures without config
• Believing build passes despite test failure

4. You added this Jenkins Pipeline step to run Selenium tests:

sh 'python3 -m selenium test_suite.py'

But the build fails with "No module named selenium" error. What is the likely fix?

medium

A. Use sh 'selenium test_suite.py' instead

B. Change command to python3 selenium test_suite.py

C. Remove -m from the command

D. Add a step to install selenium with pip install selenium before running tests

Solution

1. Step 1: Understand error cause

   "No module named selenium" means Python can't find the selenium package installed.

2. Step 2: Fix by installing selenium

   Adding pip install selenium before running tests ensures the package is available.

3. Final Answer:

   Add a step to install selenium with pip install selenium before running tests -> Option D

4. Quick Check:

   Missing package error = install package first [OK]

Hint: Install missing Python packages before running tests [OK]

Common Mistakes:

• Changing command syntax without installing package
• Removing -m which is unrelated here
• Trying to run selenium as a command

5. You want Jenkins to run Selenium Python tests on multiple browsers (Chrome and Firefox) and report results separately. Which approach is best?

hard

A. Create separate Jenkins stages for each browser running tests with different WebDriver setups

B. Run tests once and assume they work on all browsers

C. Use a single stage and switch browsers randomly during tests

D. Run tests locally and upload results manually to Jenkins

Solution

1. Step 1: Understand multi-browser testing needs

   Each browser requires its own WebDriver setup and test run to isolate results.

2. Step 2: Use separate Jenkins stages for clarity

   Separate stages for Chrome and Firefox allow clear reporting and parallel or sequential runs.

3. Final Answer:

   Create separate Jenkins stages for each browser running tests with different WebDriver setups -> Option A

4. Quick Check:

   Separate stages = clear multi-browser testing [OK]

Hint: Separate stages for each browser give clear test results [OK]

Common Mistakes:

• Running tests once for all browsers without setup
• Switching browsers randomly causing flaky tests
• Manual result uploads instead of automation