Parallel execution in CI in Selenium Python - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is parallel execution in Continuous Integration (CI)?

Parallel execution means running multiple tests at the same time during the CI process. This helps finish testing faster and find problems quickly.

beginner

Why use parallel execution in Selenium tests within CI?

Using parallel execution in Selenium tests saves time by running tests on different browsers or parts of the app at once. It makes feedback faster and improves productivity.

intermediate

Name a common tool or framework to enable parallel test execution in Python Selenium tests.

Pytest with the pytest-xdist plugin is commonly used to run Selenium tests in parallel in Python.

intermediate

What is a key challenge when running Selenium tests in parallel in CI?

A key challenge is managing shared resources like browsers or test data to avoid conflicts. Tests must be independent and isolated to run safely in parallel.

intermediate

How does parallel execution affect test reports in CI?

Parallel execution can make test reports more complex because tests finish at different times. CI tools usually combine results to show a clear summary of all tests.

What is the main benefit of parallel execution in CI?

A Faster test completion

B More detailed test logs

C Simpler test code

D Less hardware usage

Parallel execution runs tests at the same time, reducing total test time.

Which Python tool helps run Selenium tests in parallel?

A requests

B pytest-xdist

C selenium-webdriver

D unittest

pytest-xdist is a plugin for pytest that enables parallel test execution.

What must tests avoid to run safely in parallel?

A Using shared resources without isolation

B Having assertions

C Running on different browsers

D Using explicit waits

Tests must be independent and avoid sharing resources to prevent conflicts.

In CI, how are parallel test results usually shown?

A Only the first test result is shown

B Results are ignored

C Combined into a single report

D Each test result is emailed separately

CI tools combine parallel test results to give a clear summary.

Which is NOT a benefit of parallel execution?

A Faster feedback

B Reduced test time

C Better resource use

D Simpler debugging

Parallel execution can make debugging harder due to simultaneous test runs.

Explain how parallel execution works in a CI pipeline for Selenium tests.

Think about running many tests together instead of one by one.

Describe challenges and solutions when implementing parallel execution in Selenium tests on CI.

Consider what can go wrong when tests share things and how to fix it.

Practice

1. What is the main benefit of running Selenium tests in parallel during Continuous Integration (CI)?

easy

A. It reduces the total test execution time by running tests simultaneously.

B. It makes tests run slower but more accurately.

C. It ensures tests run only on one browser at a time.

D. It disables all tests except one to save resources.

Solution

1. Step 1: Understand parallel execution in CI

   Parallel execution means running multiple tests at the same time instead of one after another.

2. Step 2: Identify the benefit of parallel execution

   Running tests simultaneously saves time by reducing total test duration.

3. Final Answer:

   It reduces the total test execution time by running tests simultaneously. -> Option A

4. Quick Check:

   Parallel execution = faster testing [OK]

Hint: Parallel means running tests at the same time [OK]

Common Mistakes:

• Thinking parallel slows tests down
• Believing tests run only on one browser
• Confusing parallel with disabling tests

2. Which Python module is commonly used to run Selenium tests in parallel within a CI pipeline?

easy

A. ThreadPoolExecutor

B. unittest

C. multiprocessing

D. time

Solution

1. Step 1: Identify Python modules for parallel execution

   Python offers several modules, but ThreadPoolExecutor from concurrent.futures is popular for parallel threads.

2. Step 2: Match module to Selenium parallel testing

   ThreadPoolExecutor allows running multiple Selenium tests in parallel threads efficiently.

3. Final Answer:

   ThreadPoolExecutor -> Option A

4. Quick Check:

   ThreadPoolExecutor = parallel threads [OK]

Hint: ThreadPoolExecutor is for parallel threads in Python [OK]

Common Mistakes:

• Choosing multiprocessing which uses processes, not threads
• Selecting unittest which is a test framework, not parallel executor
• Picking time which is for delays, not parallelism

3. Given the code snippet below, what will be the output?

from concurrent.futures import ThreadPoolExecutor
import time

def test_func(name):
    time.sleep(1)
    return f"Test {name} done"

with ThreadPoolExecutor(max_workers=3) as executor:
    results = list(executor.map(test_func, ['A', 'B', 'C', 'D']))
print(results)

medium

A. Error due to max_workers less than tasks

B. ['Test A done', 'Test B done', 'Test C done']

C. ['Test A done', 'Test B done', 'Test C done', 'Test D done']

D. ['Test D done']

Solution

1. Step 1: Understand ThreadPoolExecutor with max_workers=3

   It runs up to 3 threads at once, but can handle more tasks by queuing them.

2. Step 2: Analyze executor.map behavior

   executor.map runs test_func on all 4 inputs and returns results in order after all finish.

3. Final Answer:

   ['Test A done', 'Test B done', 'Test C done', 'Test D done'] -> Option C

4. Quick Check:

   All tasks run, results list includes all [OK]

Hint: ThreadPoolExecutor queues extra tasks beyond max_workers [OK]

Common Mistakes:

• Assuming only 3 results because max_workers=3
• Expecting error due to more tasks than workers
• Thinking results order changes

4. You wrote this code to run Selenium tests in parallel but get an error: RuntimeError: cannot schedule new futures after shutdown. What is the likely cause?

from concurrent.futures import ThreadPoolExecutor
executor = ThreadPoolExecutor(max_workers=2)
executor.shutdown()
executor.submit(test_function)

medium

A. ThreadPoolExecutor requires a context manager to work.

B. max_workers=2 is too low for submitting tasks.

C. test_function is not defined before submit call.

D. Calling submit after shutdown closes the executor, so no new tasks allowed.

Solution

1. Step 1: Understand executor.shutdown() effect

   shutdown() stops the executor from accepting new tasks and cleans up threads.

2. Step 2: Analyze submit call after shutdown

   Calling submit after shutdown causes RuntimeError because executor is closed.

3. Final Answer:

   Calling submit after shutdown closes the executor, so no new tasks allowed. -> Option D

4. Quick Check:

   submit after shutdown = error [OK]

Hint: Don't submit tasks after executor.shutdown() [OK]

Common Mistakes:

• Thinking max_workers causes this error
• Assuming test_function undefined causes this error
• Believing context manager is required

5. You want to run Selenium tests in parallel on Chrome and Firefox browsers in your CI pipeline using Python. Which approach correctly sets up parallel execution for both browsers?

hard

A. Run tests sequentially by switching browser drivers inside a single test function.

B. Use ThreadPoolExecutor to run a test function twice, each time initializing a different browser driver inside the function.

C. Use a single WebDriver instance shared by all tests to save memory.

D. Run tests in parallel but initialize browsers outside the test functions to avoid overhead.

Solution

1. Step 1: Understand parallel testing with multiple browsers

   Each test must create its own browser driver instance to avoid conflicts.

2. Step 2: Use ThreadPoolExecutor to run tests in parallel

   Running test functions in parallel, each initializing its own browser, allows simultaneous testing on Chrome and Firefox.

3. Final Answer:

   Use ThreadPoolExecutor to run a test function twice, each time initializing a different browser driver inside the function. -> Option B

4. Quick Check:

   Separate drivers per thread = correct parallel setup [OK]

Hint: Initialize browser inside each parallel test function [OK]

Common Mistakes:

• Sharing one WebDriver instance across threads
• Switching browsers sequentially defeats parallelism
• Initializing browsers outside test functions causes conflicts