Parallel execution in CI in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use parallel test execution in CI?

Imagine you have 100 automated UI tests. Running them one by one takes a long time. Why is running tests in parallel in a Continuous Integration (CI) environment beneficial?

A It makes tests run slower but more reliably.

B It ensures tests run in a specific order to avoid conflicts.

C It reduces total test execution time by running multiple tests at the same time.

D It disables flaky tests automatically during execution.

💡 Hint

Think about how doing many things at once affects total time.

Parallel execution allows multiple tests to run simultaneously, reducing the total time needed to complete all tests. This speeds up feedback in CI pipelines.

❓ Predict Output

intermediate

Output of parallel test run with shared state

Consider this simplified Python Selenium test snippet run in parallel threads sharing the same WebDriver instance:

from selenium import webdriver
from threading import Thread

shared_driver = webdriver.Chrome()
results = []

def test():
    shared_driver.get('https://example.com')
    results.append(shared_driver.title)

threads = [Thread(target=test) for _ in range(2)]
for t in threads:
    t.start()
for t in threads:
    t.join()
print(results)

What is the most likely outcome?

A ['Example Domain', 'Example Domain'] - Both threads succeed using shared driver.

B RuntimeError or WebDriverException due to concurrent access to shared driver.

C [] - No titles collected because threads run before page loads.

D ['Example Domain'] - Only one thread appends result, other fails silently.

💡 Hint

Think about thread safety when sharing browser instances.

WebDriver instances are not thread-safe. Sharing one instance across threads causes errors or unpredictable behavior.

❓ locator

advanced

Best locator strategy for parallel Selenium tests

In parallel Selenium tests running on multiple browsers, which locator strategy is best to avoid flaky tests caused by dynamic page changes?

A Using unique IDs or data-test attributes for elements.

B Using absolute XPath expressions starting from the root element.

C Using CSS selectors with nth-child to locate elements by position.

D Using text-based XPath queries that match visible text.

💡 Hint

Think about stability and uniqueness of locators across test runs.

Unique IDs or dedicated data-test attributes provide stable, fast, and reliable locators that reduce flakiness in parallel tests.

❓ assertion

advanced

Correct assertion for parallel test results aggregation

You run 5 parallel Selenium tests that each return a boolean pass/fail result. You collect results in a list results. Which assertion correctly verifies all tests passed?

Selenium Python

results = [True, True, True, True, True]

A assert all(results) == True

B assert results is True

C assert any(results) == True

D assert results == True

💡 Hint

Check how to verify all items in a list are True.

all(results) returns True only if every item in the list is True. This correctly asserts all tests passed.

❓ framework

expert

Configuring pytest-xdist for parallel Selenium tests in CI

You want to run Selenium tests in parallel on 4 workers using pytest-xdist in a CI pipeline. Which pytest command correctly runs tests in parallel with 4 workers?

A pytest -w 4

B pytest --workers=4

C pytest --parallel=4

D pytest -n 4

💡 Hint

Check pytest-xdist documentation for the parallel option syntax.

The -n option followed by a number specifies the number of parallel workers in pytest-xdist.