Fixture scope with parallel tests in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding fixture scope behavior in parallel pytest runs

In pytest, when running tests in parallel using pytest-xdist, which fixture scope ensures that a fixture is created once per worker process?

A function

B session

C module

D package

💡 Hint

Think about the widest scope that pytest-xdist respects per worker.

The session scope creates the fixture once per worker process when running tests in parallel with pytest-xdist. Other scopes like module or function create fixtures more frequently.

❓ Predict Output

intermediate

Output of fixture usage with 'module' scope in parallel tests

Consider this pytest code run with 2 parallel workers using pytest-xdist:

import pytest

@pytest.fixture(scope='module')
def resource():
    print('Setup resource')
    yield
    print('Teardown resource')

def test_one(resource):
    pass

def test_two(resource):
    pass

How many times will 'Setup resource' be printed?

A 0

B 1

C 4

D 2

💡 Hint

Remember that each worker runs tests independently and module scope is per module per worker.

With 2 workers, each runs the module's tests once, so the module-scoped fixture setup runs once per worker, totaling 2 times.

❓ assertion

advanced

Correct assertion for fixture usage count in parallel tests

You want to assert that a fixture with 'session' scope is created exactly once per worker when running 3 parallel pytest workers.

Which assertion correctly verifies this if setup_count tracks the number of fixture setups?

PyTest

def test_fixture_count(setup_count):
    # assert here
    pass

A assert setup_count == 3

B assert setup_count == 1

C assert setup_count >= 3

D assert setup_count <= 1

💡 Hint

Each worker runs its own session-scoped fixture instance.

With 3 workers, each creates its own session-scoped fixture, so the total setup count should be 3.

🔧 Debug

advanced

Debugging fixture sharing issue in parallel pytest

You have a fixture with 'session' scope but notice it runs multiple times when running tests in parallel with pytest-xdist. What is the most likely cause?

A The fixture scope is ignored when using pytest-xdist

B The fixture is defined inside a test function, causing multiple runs

C Each worker process has its own session, so fixture runs once per worker

D The fixture uses yield instead of return, causing multiple setups

💡 Hint

Think about how pytest-xdist manages processes.

pytest-xdist runs tests in separate worker processes, each with its own session. So session-scoped fixtures run once per worker, not globally.

❓ framework

expert

Best practice for sharing expensive fixture setup across parallel pytest workers

You have an expensive setup fixture that you want to share across all parallel pytest workers to avoid repeated setup. Which approach is best?

A Use a session-scoped fixture combined with a shared external resource like a database or file system lock

B Set fixture scope to 'function' and rely on pytest-xdist to optimize

C Use module-scoped fixtures and run tests sequentially

D Use pytest's cache to store fixture state between workers automatically

💡 Hint

Think about sharing state beyond process boundaries.

pytest fixtures run per worker process; to share expensive setup, use external shared resources or locks combined with session scope.

Practice

1. What does the scope='session' parameter in a pytest fixture control?

easy

A. The fixture runs once per entire test session.

B. The fixture runs once per test function.

C. The fixture runs once per test class.

D. The fixture runs once per test module.

Solution

1. Step 1: Understand fixture scopes in pytest

   Pytest fixtures can have different scopes like function, class, module, and session, which control how often the fixture setup runs.

2. Step 2: Identify what session scope means

   Session scope means the fixture runs only once for the entire test session, regardless of how many tests use it.

3. Final Answer:

   The fixture runs once per entire test session. -> Option A

4. Quick Check:

   scope='session' = runs once per session [OK]

Hint: Session scope means one setup for all tests in session [OK]

Common Mistakes:

• Confusing session scope with function scope
• Thinking session scope runs per test module
• Assuming session scope runs per test class

2. Which of the following is the correct syntax to define a pytest fixture with session scope?

easy

A. @pytest.fixture(scope='function')

B. @pytest.fixture(scope='session')

C. @pytest.fixture(session=True)

D. @pytest.fixture(scope=session)

Solution

1. Step 1: Recall pytest fixture syntax

   Pytest fixtures use the decorator @pytest.fixture() with optional parameters like scope as a string.

2. Step 2: Identify correct scope parameter usage

   The scope parameter must be a string, so scope='session' is correct. Options C and D are invalid syntax.

3. Final Answer:

   @pytest.fixture(scope='session') -> Option B

4. Quick Check:

   Correct syntax uses scope='session' string [OK]

Hint: Use quotes around scope value: scope='session' [OK]

Common Mistakes:

• Omitting quotes around 'session'
• Using invalid keyword arguments
• Confusing scope with boolean flags

3. Consider this pytest fixture and test code run with 2 parallel workers:

@pytest.fixture(scope='session')
def resource():
    print('Setup resource')
    yield
    print('Teardown resource')

def test_a(resource):
    pass

def test_b(resource):
    pass

How many times will 'Setup resource' be printed during the entire test run?

medium

A. Once

B. Zero times

C. Twice

D. Four times

Solution

1. Step 1: Understand session scope with parallel workers

   When running tests in parallel with pytest-xdist, each worker runs its own session, so session-scoped fixtures run once per worker.

2. Step 2: Calculate total setup calls

   With 2 workers, the fixture setup runs once per worker, so 'Setup resource' prints twice.

3. Final Answer:

   Twice -> Option C

4. Quick Check:

   Session scope runs once per worker = 2 times [OK]

Hint: Session scope runs once per worker in parallel tests [OK]

Common Mistakes:

• Assuming session scope runs only once globally
• Ignoring parallel worker count
• Confusing function scope with session scope

4. You have a session-scoped fixture used in parallel tests with 3 workers. You notice the fixture setup runs 3 times, but you want it to run only once globally. What is the likely cause and fix?

medium

A. Cause: fixture is not used; Fix: add fixture to tests.

B. Cause: fixture scope is function; Fix: change to session scope.

C. Cause: parallel tests disabled; Fix: enable parallel execution.

D. Cause: session scope runs per worker; Fix: use a database or external service to share state.

Solution

1. Step 1: Identify why session scope runs multiple times

   In parallel testing, session scope runs once per worker, so with 3 workers, setup runs 3 times.

2. Step 2: Understand how to share fixture state globally

   To run setup only once globally, you must share state outside pytest workers, e.g., via a database or external service.

3. Final Answer:

   Cause: session scope runs per worker; Fix: use a database or external service to share state. -> Option D

4. Quick Check:

   Session scope per worker needs external sharing [OK]

Hint: Session scope runs per worker; share state externally to fix [OK]

Common Mistakes:

• Thinking session scope runs once globally in parallel
• Changing scope to function instead of sharing state
• Ignoring parallel execution effects

5. You want to run expensive setup code only once for all tests across 4 parallel pytest workers. Which approach correctly ensures this behavior?

hard

A. Use scope='session' fixture and implement external resource locking (e.g., file lock or database).

B. Use scope='function' fixture and cache results in a global variable.

C. Use scope='session' fixture and rely on pytest-xdist to share it automatically.

D. Use scope='module' fixture and run tests sequentially.

Solution

1. Step 1: Understand session scope behavior with parallel workers

   Session scope runs once per worker, so with 4 workers, setup runs 4 times unless shared externally.

2. Step 2: Identify how to run setup only once globally

   Implementing external resource locking (like a file lock or database flag) ensures only one worker runs the expensive setup.

3. Final Answer:

   Use scope='session' fixture and implement external resource locking (e.g., file lock or database). -> Option A

4. Quick Check:

   External locking + session scope = single global setup [OK]

Hint: Combine session scope with external locking for global setup [OK]

Common Mistakes:

• Assuming pytest-xdist shares session fixtures automatically
• Using function scope and expecting single setup
• Running tests sequentially defeats parallel purpose