pytest-xdist for parallel execution - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of pytest-xdist parallel test run

Given the following pytest test file and running it with pytest-xdist using 2 workers, what will be the output summary line?

PyTest

import time
import pytest

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

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

A 2 passed in ~1 second

B 1 passed, 1 failed in ~1 second

C 2 passed in ~2 seconds

D Tests skipped due to worker error

💡 Hint

Think about how parallel execution affects total test time.

Using pytest-xdist with 2 workers runs tests in parallel, so total time is about the longest single test, not the sum.

❓ assertion

intermediate

Correct assertion for parallel test results

You run pytest with xdist -n 3 on 6 tests. Which assertion correctly checks that all tests passed?

A assert result.testscollected == 3 and result.testsfailed == 0

B assert result.testscollected == 6 and result.testsfailed > 0

C assert result.testscollected == 6 and result.testsfailed == 0

D assert result.testscollected == 0 and result.testsfailed == 0

💡 Hint

Total tests collected is independent of number of workers.

All 6 tests should be collected and none failed if all passed.

🔧 Debug

advanced

Identify cause of flaky test with pytest-xdist

You notice tests sometimes fail when run with pytest-xdist -n 4 but pass when run normally. What is the most likely cause?

A pytest-xdist disables assertions

B pytest-xdist does not support parallel execution

C Tests are too fast to run in parallel

D Tests share and modify global state causing race conditions

💡 Hint

Think about what changes when tests run in parallel.

Parallel tests can interfere if they share mutable global data without isolation.

❓ framework

advanced

Best practice for using pytest-xdist with database tests

When running database tests in parallel with pytest-xdist, what is the best practice to avoid conflicts?

A Disable transactions in tests

B Use separate database instances or schemas per worker

C Use a single shared database connection for all tests

D Run all tests sequentially to avoid conflicts

💡 Hint

Think about how parallel tests can interfere with shared resources.

Isolating database state per worker prevents data conflicts and test interference.

🧠 Conceptual

expert

Understanding pytest-xdist load scheduling modes

pytest-xdist supports different load scheduling modes. Which mode dynamically assigns tests to workers as they finish, improving load balance?

A Load scheduling mode

B Static scheduling mode

C Round-robin scheduling mode

D Batch scheduling mode

💡 Hint

One mode assigns tests dynamically to balance workload.

Load scheduling mode assigns tests to free workers dynamically, reducing idle time.

Practice

1. What is the main purpose of using pytest-xdist in test execution?

easy

A. To run tests in parallel and reduce total test time

B. To generate detailed HTML reports

C. To automatically fix failing tests

D. To run tests only on a single CPU core

Solution

1. Step 1: Understand pytest-xdist functionality

   pytest-xdist allows running tests simultaneously on multiple CPU cores.

2. Step 2: Identify the benefit of parallel execution

   Running tests in parallel reduces the total time needed to complete all tests.

3. Final Answer:

   To run tests in parallel and reduce total test time -> Option A

4. Quick Check:

   pytest-xdist = parallel test execution [OK]

Hint: Remember: xdist means 'distributed' tests run together [OK]

Common Mistakes:

• Confusing xdist with report generation tools
• Thinking xdist fixes test code automatically
• Assuming xdist runs tests sequentially

2. Which command correctly runs tests in parallel using 4 workers with pytest-xdist?

easy

A. pytest -n 4

B. pytest --workers=4

C. pytest -p 4

D. pytest --parallel 4

Solution

1. Step 1: Recall pytest-xdist syntax for parallelism

   The correct flag to specify number of parallel workers is -n.

2. Step 2: Match the correct command

   pytest -n 4 runs tests with 4 parallel workers.

3. Final Answer:

   pytest -n 4 -> Option A

4. Quick Check:

   -n sets workers = C [OK]

Hint: Use '-n' to set number of parallel workers [OK]

Common Mistakes:

• Using incorrect flags like --workers or --parallel
• Confusing -p (plugin) with -n
• Omitting the number after -n

3. Given this pytest command: pytest -n 3 test_sample.py, what happens during test execution?

medium

A. Tests run in parallel but limited to 1 CPU core

B. Tests in test_sample.py run sequentially on one CPU core

C. Only 3 tests from test_sample.py run sequentially

D. Tests in test_sample.py run in parallel using 3 CPU cores

Solution

1. Step 1: Analyze the command options

   The -n 3 option tells pytest-xdist to use 3 workers for parallel execution.

2. Step 2: Understand effect on test_sample.py

   All tests in test_sample.py are distributed across 3 CPU cores and run simultaneously.

3. Final Answer:

   Tests in test_sample.py run in parallel using 3 CPU cores -> Option D

4. Quick Check:

   -n 3 means 3 parallel workers = A [OK]

Hint: -n sets parallel workers, all tests split among them [OK]

Common Mistakes:

• Thinking only 3 tests run instead of all tests
• Assuming tests run sequentially despite -n
• Confusing number of workers with number of tests

4. You run pytest -n 2 but get an error: ERROR: unknown option: -n. What is the likely cause?

medium

A. You used the wrong flag; it should be --num

B. pytest-xdist plugin is not installed

C. You need to run pytest with sudo

D. The test files are missing

Solution

1. Step 1: Understand the error message

   The error says -n is unknown, meaning pytest does not recognize the option.

2. Step 2: Identify cause related to pytest-xdist

   The -n option is provided by pytest-xdist plugin. If it's not installed, pytest won't recognize it.

3. Final Answer:

   pytest-xdist plugin is not installed -> Option B

4. Quick Check:

   Unknown -n means missing xdist plugin = B [OK]

Hint: Install pytest-xdist to enable -n option [OK]

Common Mistakes:

• Assuming -n flag is built-in pytest option
• Trying to run with sudo unnecessarily
• Ignoring plugin installation step

5. You want to speed up a large test suite using pytest-xdist but notice flaky failures when running with pytest -n auto. What is a good approach to fix this?

hard

A. Disable pytest-xdist and run tests sequentially

B. Increase the number of workers beyond CPU cores

C. Add @pytest.mark.serial to tests that share state to run them sequentially

D. Use pytest -n 1 to force single worker

Solution

1. Step 1: Understand cause of flaky failures

   Tests sharing state or resources can fail when run in parallel due to conflicts.

2. Step 2: Use markers to run conflicting tests sequentially

   Marking such tests with @pytest.mark.serial (or similar) ensures they run one at a time, avoiding conflicts.

3. Step 3: Keep parallelism for other tests

   This approach balances speed and stability by running safe tests in parallel and conflicting ones sequentially.

4. Final Answer:

   Add @pytest.mark.serial to tests that share state to run them sequentially -> Option C

5. Quick Check:

   Mark shared-state tests serial to fix flakes = A [OK]

Hint: Mark shared tests serial to avoid parallel conflicts [OK]

Common Mistakes:

• Blindly increasing workers causing more flakes
• Disabling parallelism losing speed benefits
• Using -n 1 which is just sequential run