Docker containers for test execution in Selenium Python

Introduction

Docker containers help run tests in a clean, controlled space. This makes tests reliable and easy to share.

You want to run Selenium tests on different machines without setup problems.

You need to test on a specific browser version without installing it locally.

You want to run tests in the cloud or on a server easily.

You want to keep your computer clean from test tools and browsers.

You want to share your test setup with teammates exactly as it is.

Syntax

Selenium Python

docker run -d -p 4444:4444 selenium/standalone-chrome

# Run your Selenium Python test script connecting to http://localhost:4444/wd/hub

This command starts a Docker container with Chrome and Selenium server ready.

Tests connect to the Selenium server URL inside the container.

Examples

Starts a container with Firefox browser for Selenium tests.

Selenium Python

docker run -d -p 4444:4444 selenium/standalone-firefox

Starts Chrome container with more shared memory to avoid crashes in heavy tests.

Selenium Python

docker run -d -p 4444:4444 --shm-size=2g selenium/standalone-chrome

Mounts your local test folder inside the container for easy access.

Selenium Python

docker run -d -p 4444:4444 -v /my/tests:/tests selenium/standalone-chrome

Sample Program

This Python script connects to the Selenium server running inside the Docker container. It opens example.com, checks the main heading, and prints a success message if the test passes.

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By

# Connect to Selenium server in Docker
options = webdriver.ChromeOptions()
remote_url = 'http://localhost:4444/wd/hub'

# Create remote WebDriver
with webdriver.Remote(command_executor=remote_url, options=options) as driver:
    driver.get('https://example.com')
    heading = driver.find_element(By.TAG_NAME, 'h1').text
    assert heading == 'Example Domain', f'Heading was {heading}'
    print('Test passed: Heading is correct')

Important Notes

Make sure Docker is installed and running before starting containers.

Use the correct Selenium image version to match your browser and Selenium client versions.

Expose the container port (usually 4444) to connect your test scripts.

Summary

Docker containers create a clean environment for running Selenium tests.

They help avoid setup issues and make tests portable.

Connect your Selenium Python tests to the container's Selenium server URL.

Practice

1. What is the main benefit of using Docker containers for Selenium test execution?

easy

A. They replace the need for writing test scripts

B. They provide a clean, consistent environment for tests to run

C. They automatically fix test failures

D. They make tests run faster on any machine

Solution

1. Step 1: Understand Docker container purpose

   Docker containers isolate the environment so tests run the same everywhere.

2. Step 2: Compare options

   Only They provide a clean, consistent environment for tests to run correctly describes this benefit; others are incorrect or unrelated.

3. Final Answer:

   They provide a clean, consistent environment for tests to run -> Option B

4. Quick Check:

   Docker containers = consistent test environment [OK]

Hint: Docker isolates environment to avoid setup issues [OK]

Common Mistakes:

• Thinking Docker speeds up tests automatically
• Believing Docker fixes test code errors
• Confusing Docker with test script writing

2. Which Python Selenium WebDriver URL should you use to connect to a Selenium server running inside a Docker container?

easy

A. "http://localhost:4444/wd/hub"

B. "http://127.0.0.1:8080"

C. "http://docker:5555"

D. "http://0.0.0.0:80"

Solution

1. Step 1: Identify default Selenium server URL in Docker

   The Selenium server in Docker usually listens on port 4444 at localhost.

2. Step 2: Match URL options

   Only "http://localhost:4444/wd/hub" matches the standard Selenium Docker URL format.

3. Final Answer:

   "http://localhost:4444/wd/hub" -> Option A

4. Quick Check:

   Default Selenium Docker URL = localhost:4444/wd/hub [OK]

Hint: Selenium Docker server default port is 4444 [OK]

Common Mistakes:

• Using wrong port numbers
• Using IPs other than localhost
• Missing the /wd/hub path

3. Given this Python code snippet connecting to a Selenium Docker container, what will be the output if the container is not running?

from selenium import webdriver
from selenium.common.exceptions import WebDriverException

try:
    driver = webdriver.Remote(
        command_executor='http://localhost:4444/wd/hub',
        options=webdriver.ChromeOptions()
    )
    print("Connected")
except WebDriverException:
    print("Connection failed")

medium

A. Connection failed

B. Connected

C. SyntaxError

D. TimeoutError

Solution

1. Step 1: Understand connection attempt

   The code tries to connect to Selenium server at localhost:4444.

2. Step 2: Consider container not running

   If the container is down, connection fails and WebDriverException is raised, triggering except block.

3. Final Answer:

   Connection failed -> Option A

4. Quick Check:

   Container down causes WebDriverException = "Connection failed" [OK]

Hint: If container off, connection throws WebDriverException [OK]

Common Mistakes:

• Expecting 'Connected' even if container is off
• Confusing exception types
• Thinking code has syntax errors

4. You wrote this Docker command to run Selenium server:

docker run -d -p 4444:4444 selenium/standalone-chrome

But your Selenium Python tests fail to connect. What is the most likely issue?

medium

A. You used the wrong port mapping in Docker command

B. You forgot to install Selenium Python package

C. Docker container is not running or crashed

D. Your test code uses an incorrect WebDriver import

Solution

1. Step 1: Check Docker container status

   If tests can't connect, first check if container is running or crashed.

2. Step 2: Evaluate other options

   The other options are less likely because the Docker command uses correct port mapping and Selenium package or imports cause different errors.

3. Final Answer:

   Docker container is not running or crashed -> Option C

4. Quick Check:

   Connection fails if container stopped = Docker container is not running or crashed [OK]

Hint: Check container running status first when connection fails [OK]

Common Mistakes:

• Assuming code import errors cause connection failure
• Ignoring container crash possibility
• Confusing port mapping syntax

5. You want to run multiple Selenium Python tests in parallel using Docker containers. Which approach best ensures isolated, reliable test runs?

hard

A. Run tests locally without Docker to avoid container overhead

B. Run all tests in a single container sharing the same browser session

C. Use Docker but share the same Selenium server URL for all tests

D. Run one Docker container per test with unique ports and clean state

Solution

1. Step 1: Understand parallel test isolation

   Running one container per test ensures each test has a clean browser and no interference.

2. Step 2: Evaluate other options

   Sharing containers or sessions risks test interference and flaky results; running locally loses Docker benefits.

3. Final Answer:

   Run one Docker container per test with unique ports and clean state -> Option D

4. Quick Check:

   Parallel tests need isolated containers = Run one Docker container per test with unique ports and clean state [OK]

Hint: Use separate containers per test for isolation [OK]

Common Mistakes:

• Sharing one container causing test conflicts
• Ignoring container cleanup between tests
• Running tests locally losing environment consistency