Parallel execution in CI in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Understanding pytest-xdist parallel test execution output

Given the pytest command below executed with pytest-xdist for parallel testing:

pytest -n 3 test_sample.py

What is the expected output behavior regarding test distribution?

PyTest

import time
import pytest

def test_one():
    time.sleep(1)
    assert True

def test_two():
    time.sleep(1)
    assert True

def test_three():
    time.sleep(1)
    assert True

A Tests run sequentially but pytest-xdist reports parallel execution without speedup.

B All three tests run sequentially on the same worker, taking about 3 seconds total.

C Tests run in parallel but only two workers are used, taking about 2 seconds total.

D Tests run in parallel across 3 workers, completing in about 1 second total.

💡 Hint

pytest-xdist distributes tests across workers to run them simultaneously.

Using '-n 3' with pytest-xdist runs tests on 3 parallel workers. Each test sleeps 1 second, so total time is about 1 second, not 3.

❓ assertion

intermediate

Choosing the correct assertion for parallel test logs

In a CI pipeline running tests in parallel, which assertion best verifies that all test logs contain the string 'PASSED' exactly once per test?

PyTest

logs = ['test_one PASSED', 'test_two PASSED', 'test_three PASSED']

A assert logs == ['PASSED', 'PASSED', 'PASSED']

B assert all('PASSED' in log for log in logs)

C assert logs.count('PASSED') == 3

D assert any('PASSED' in log for log in logs)

💡 Hint

Check each log individually for the substring.

Option B checks that every log string contains 'PASSED'. Option B is invalid because logs is a list of strings, not a list of 'PASSED'. Option B expects exact strings, which is incorrect. Option B only checks if any log contains 'PASSED', not all.

🔧 Debug

advanced

Debugging flaky tests in parallel CI runs

A test suite runs fine locally but intermittently fails in CI when run with pytest-xdist parallel execution. Which is the most likely cause?

A Tests share global state or resources causing race conditions.

B pytest-xdist does not support parallel execution on CI servers.

C The test code has syntax errors that only appear in CI.

D The CI server has insufficient CPU cores to run tests.

💡 Hint

Parallel tests must avoid shared mutable state.

Flaky failures in parallel runs often come from tests sharing global variables or files, causing race conditions. pytest-xdist supports parallel runs on CI. Syntax errors cause consistent failures. CPU cores affect speed but not correctness.

❓ framework

advanced

Configuring pytest for parallel execution in CI

Which pytest configuration snippet correctly enables parallel test execution with 4 workers in a CI environment?

A

[pytest]
addopts = -n 4 --dist=loadfile

B

[pytest]
addopts = --workers=4 --dist=loadfile

C

[pytest]
addopts = -n 4 --dist=loadscope

D

[pytest]
addopts = --parallel=4 --dist=loadscope

💡 Hint

The '-n' option sets the number of workers.

Option A uses '-n 4' to specify 4 workers and '--dist=loadfile' to distribute tests by file, which is valid. Option A uses invalid '--dist=loadscope'. Option A uses invalid '--workers'. Option A uses invalid '--parallel'.

🧠 Conceptual

expert

Impact of parallel test execution on test isolation in CI

Why is test isolation especially critical when running tests in parallel in a CI pipeline?

A Because isolated tests require more CPU resources in parallel.

B Because parallel tests always run slower, isolation improves speed.

C Because parallel tests may run simultaneously, shared state can cause unpredictable failures.

D Because CI pipelines do not support parallel execution without isolation.

💡 Hint

Think about what happens if tests share data at the same time.

Parallel tests run at the same time, so if they share state or resources, they can interfere and cause random failures. Isolation prevents this by keeping tests independent.