Running Selenium in CI pipeline in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Selenium WebDriver in headless mode

What will be the output when running this Selenium Python script in a CI pipeline with headless Chrome?

Selenium Python

from selenium import webdriver
from selenium.webdriver.chrome.options import Options

options = Options()
options.add_argument('--headless')
driver = webdriver.Chrome(options=options)
driver.get('https://example.com')
title = driver.title
driver.quit()
print(title)

A Example Domain

B selenium.common.exceptions.WebDriverException

C No output (script hangs)

D ChromeDriver not found error

💡 Hint

Headless mode allows Chrome to run without opening a window, so the page title can still be retrieved.

The script runs Chrome in headless mode, navigates to example.com, and prints the page title 'Example Domain'.

❓ Troubleshoot

intermediate

Fixing ChromeDriver version mismatch error in CI

In a CI pipeline, Selenium tests fail with the error: 'This version of ChromeDriver only supports Chrome version 90'. What is the best way to fix this?

A Remove the --headless argument from Chrome options

B Downgrade Selenium to an older version

C Update ChromeDriver to match the installed Chrome browser version

D Increase the timeout for WebDriver initialization

💡 Hint

ChromeDriver and Chrome browser versions must be compatible.

The error occurs because ChromeDriver version does not match the installed Chrome browser version. Updating ChromeDriver to the correct version resolves this.

❓ Configuration

advanced

Configuring Selenium to run with Firefox in CI

Which configuration snippet correctly sets up Selenium WebDriver to run Firefox in headless mode in a CI pipeline?

A

from selenium import webdriver
from selenium.webdriver.firefox.options import Options
options = Options()
options.headless = True
driver = webdriver.Firefox(options=options)

B

from selenium import webdriver
options = webdriver.FirefoxOptions()
options.add_argument('--headless')
driver = webdriver.Firefox(options=options)

C

from selenium import webdriver
options = webdriver.FirefoxOptions()
options.headless = True
driver = webdriver.Firefox(options=options)

D

from selenium import webdriver
from selenium.webdriver.firefox.options import Options
options = Options()
options.add_argument('--headless')
driver = webdriver.Firefox(options=options)

💡 Hint

Use the correct import and method to add headless argument for Firefox.

Option D correctly imports Options, adds '--headless' argument, and passes options to Firefox WebDriver.

🔀 Workflow

advanced

Best CI workflow step to run Selenium tests

In a CI pipeline, which step order ensures Selenium tests run reliably with Chrome in headless mode?

A Run Selenium tests -> Install Chrome -> Install ChromeDriver -> Cleanup

B Install Chrome -> Install ChromeDriver -> Run Selenium tests -> Cleanup

C Install ChromeDriver -> Install Chrome -> Run Selenium tests -> Cleanup

D Install Chrome -> Run Selenium tests -> Install ChromeDriver -> Cleanup

💡 Hint

Chrome and ChromeDriver must be installed before running tests.

Tests require Chrome and ChromeDriver installed first. Running tests before installation causes failure.

🧠 Conceptual

expert

Why use virtual display (Xvfb) in Selenium CI pipelines?

What is the main reason to use a virtual display like Xvfb when running Selenium tests in CI pipelines on Linux servers?

A To provide a graphical environment for browsers to run without a physical display

B To speed up browser startup time by caching display data

C To enable running tests in parallel on multiple CPU cores

D To automatically update browser drivers to the latest version

💡 Hint

Linux servers often lack a graphical desktop environment.

Xvfb creates a virtual framebuffer so browsers can run graphical tests without needing a real display.

Practice

1. Why is it important to run Selenium tests in a CI pipeline?

easy

A. To slow down the deployment process

B. To automatically catch bugs early during development

C. To manually check the UI after deployment

D. To avoid writing test scripts

Solution

1. Step 1: Understand the purpose of CI pipelines

   CI pipelines automate testing and building to catch issues early.

2. Step 2: Relate Selenium tests to CI benefits

   Running Selenium tests in CI helps find UI bugs automatically before release.

3. Final Answer:

   To automatically catch bugs early during development -> Option B

4. Quick Check:

   CI + Selenium = Early bug detection [OK]

Hint: CI runs tests automatically to catch bugs early [OK]

Common Mistakes:

• Thinking CI slows deployment
• Believing tests run manually in CI
• Ignoring automated testing benefits

2. Which of the following is the correct way to run Chrome in headless mode in Selenium Python?

easy

A. options.add_argument('--headless')

B. options.set_headless(True)

C. driver.headless = True

D. driver.set_option('headless')

Solution

1. Step 1: Recall Selenium ChromeOptions usage

   To run Chrome headless, add the argument '--headless' to options.

2. Step 2: Verify correct syntax

   Using options.add_argument('--headless') is the correct method in Selenium Python.

3. Final Answer:

   options.add_argument('--headless') -> Option A

4. Quick Check:

   Headless Chrome = add_argument('--headless') [OK]

Hint: Use add_argument('--headless') to enable headless mode [OK]

Common Mistakes:

• Using non-existent methods like set_headless
• Trying to set driver.headless directly
• Confusing driver and options methods

3. What will be the output when running this Selenium Python snippet in a CI environment without a display server?

from selenium import webdriver
from selenium.webdriver.chrome.options import Options
options = Options()
options.add_argument('--headless')
driver = webdriver.Chrome(options=options)
driver.get('https://example.com')
print(driver.title)
driver.quit()

medium

A. Prints 'ChromeDriver not found' error

B. Throws an error about missing display server

C. Prints an empty string

D. Prints the page title 'Example Domain'

Solution

1. Step 1: Understand headless mode effect

   Headless mode allows Chrome to run without a display server in CI.

2. Step 2: Analyze code behavior

   The code opens example.com headlessly and prints the page title successfully.

3. Final Answer:

   Prints the page title 'Example Domain' -> Option D

4. Quick Check:

   Headless mode avoids display errors, prints title [OK]

Hint: Headless mode avoids display errors, so title prints [OK]

Common Mistakes:

• Assuming display server is always needed
• Expecting empty output without display
• Confusing driver errors with headless mode

4. You added Selenium tests to your CI pipeline but they fail with the error: selenium.common.exceptions.WebDriverException: Message: 'chromedriver' executable needs to be in PATH. How do you fix this?

medium

A. Install ChromeDriver and add it to the system PATH in the CI environment

B. Remove the ChromeDriver and use Firefox instead

C. Run tests without specifying any driver

D. Disable headless mode in Chrome options

Solution

1. Step 1: Understand the error message

   The error says ChromeDriver is missing or not found in PATH.

2. Step 2: Fix by installing ChromeDriver in CI

   Install ChromeDriver and ensure its location is in the PATH environment variable.

3. Final Answer:

   Install ChromeDriver and add it to the system PATH in the CI environment -> Option A

4. Quick Check:

   Driver missing error = install and add to PATH [OK]

Hint: Add ChromeDriver to PATH in CI to fix driver not found [OK]

Common Mistakes:

• Ignoring driver installation
• Switching browsers without fixing driver
• Disabling headless mode unrelated to driver error

5. You want to run Selenium tests in a CI pipeline using Docker. Which setup ensures tests run headlessly and ChromeDriver is available inside the container?

hard

A. Run Selenium tests on host machine, not inside Docker

B. Use a plain Python image and install ChromeDriver only, no Chrome needed

C. Use a Docker image with Chrome and ChromeDriver installed, run Chrome with '--headless' option in Selenium

D. Use Firefox without headless mode inside Docker container

Solution

1. Step 1: Identify requirements for Selenium in Docker

   Tests need both Chrome browser and ChromeDriver installed inside the container.

2. Step 2: Choose correct Docker setup

   A Docker image with Chrome and ChromeDriver pre-installed and running Chrome headless is best practice.

3. Final Answer:

   Use a Docker image with Chrome and ChromeDriver installed, run Chrome with '--headless' option in Selenium -> Option C

4. Quick Check:

   Docker Selenium needs browser + driver + headless [OK]

Hint: Docker needs both Chrome and ChromeDriver installed [OK]

Common Mistakes:

• Installing driver without browser
• Running tests outside Docker when container needed
• Using non-headless mode in CI Docker