Jenkins integration in Selenium Python - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Jenkins library in Python.

Selenium Python

import [1]

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

Arequests

Bjenkinsapi

Cselenium

Djenkins

Attempts:

3 left

💡 Hint

Common Mistakes

Using selenium instead of jenkins for Jenkins integration.

Importing requests which is for HTTP calls but not Jenkins specific.

The jenkins library is used to interact with Jenkins servers in Python.

2fill in blank

medium

Complete the code to create a Jenkins server object with URL 'http://localhost:8080'.

Selenium Python

server = jenkins.Jenkins([1])

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

A'http://127.0.0.1:8080'

B'http://0.0.0.0:8080'

C'http://localhost:8080'

D'http://jenkins.local:8080'

Attempts:

3 left

💡 Hint

Common Mistakes

Using IP address instead of 'localhost'.

Forgetting quotes around the URL string.

The Jenkins server URL is usually 'http://localhost:8080' when running locally.

3fill in blank

hard

Fix the error in the code to trigger a Jenkins build for job 'TestJob'.

Selenium Python

server.[1]('TestJob')

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

Abuild_job

Btrigger_build

Cstart_build

Drun_job

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'start_build' or 'run_job'.

Confusing method names that do not exist in the Jenkins API.

The correct method to start a Jenkins job build is build_job.

4fill in blank

hard

Fill both blanks to check if the last build of 'DeployJob' was successful.

Selenium Python

last_build_number = server.get_job_info('DeployJob')['[1]']['number']
status = server.get_build_info('DeployJob', last_build_number)['[2]']

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

AlastBuild

Bresult

CbuildStatus

Dlast_build

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect keys like 'buildStatus' or 'last_build'.

Confusing the keys for job info and build info.

The key to get the last build number is lastBuild. The build result status is under result.

5fill in blank

hard

Fill all three blanks to trigger a build with parameters for job 'TestJob'.

Selenium Python

params = {'branch': 'main', 'env': 'staging'}
server.[1]('TestJob', [2]=[3])

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

Abuild_job

Bparameters

Cparams

Dbuild_with_parameters

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'build_with_parameters' instead of 'build_job'.

Mixing up argument names and variable names.

To trigger a parameterized build, use build_job method with parameters=params.

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