Docker containers for test execution in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use Docker containers for Selenium test execution?

Which of the following is the main advantage of running Selenium tests inside Docker containers?

A It makes tests run faster by using the host's GPU directly.

B It automatically writes test reports without any configuration.

C It ensures tests run in a consistent environment regardless of the host machine.

D It eliminates the need for writing assertions in tests.

💡 Hint

Think about how Docker isolates environments.

Docker containers package the browser, drivers, and dependencies so tests run the same way everywhere.

❓ Predict Output

intermediate

Output of Selenium test inside Docker with missing driver

What will be the output when running this Selenium Python test inside a Docker container missing the ChromeDriver binary?

Selenium Python

from selenium import webdriver

driver = webdriver.Chrome()
driver.get('https://example.com')
print(driver.title)
driver.quit()

A TypeError: 'Service' object is not callable.

B selenium.common.exceptions.WebDriverException: Message: 'chromedriver' executable needs to be in PATH.

C The page title 'Example Domain' is printed successfully.

D TimeoutException: Page load timed out.

💡 Hint

Check if the driver binary is available inside the container.

If ChromeDriver is missing inside the Docker container, Selenium raises a WebDriverException about the executable.

❓ locator

advanced

Best locator strategy for flaky tests in Docker Selenium

Which locator strategy is most reliable to reduce flaky Selenium tests running inside Docker containers?

A Using index-based locators like find_elements_by_tag_name('button')[3].

B Using XPath with absolute paths like '/html/body/div[2]/div[1]/button'.

C Using JavaScript execution to find elements dynamically.

D Using CSS selectors with stable IDs or classes like '#submit-button'.

💡 Hint

Think about selectors that are less likely to change.

CSS selectors with stable IDs or classes are less brittle and reduce flakiness compared to absolute XPath or index-based locators.

❓ assertion

advanced

Correct assertion for page title in Selenium test inside Docker

Which assertion correctly verifies the page title is exactly 'Welcome Page' in a Selenium Python test running inside Docker?

Selenium Python

driver.get('https://example.com/welcome')
page_title = driver.title

A assert page_title == 'Welcome Page'

B assert 'Welcome' in page_title

C assert page_title != 'Welcome Page'

D assert page_title.startswith('Welcome')

💡 Hint

Check for exact match, not partial or negation.

To verify the title exactly matches 'Welcome Page', use equality assertion. Other options check partial or wrong conditions.

❓ framework

expert

Handling parallel Selenium tests in Docker containers

You want to run multiple Selenium tests in parallel using Docker containers. Which approach best ensures isolated browser sessions and avoids port conflicts?

A Run each test in its own Docker container with unique exposed ports and separate browser instances.

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

C Run tests sequentially in one container to avoid conflicts.

D Use Docker volumes to share browser profiles between tests.

💡 Hint

Think about isolation and resource conflicts in parallel execution.

Running each test in its own container with unique ports ensures isolation and prevents conflicts during parallel execution.

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