Ordering tests for parallel safety in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is test ordering important in parallel test execution?

When running tests in parallel, why must the order of tests be carefully managed?

A Because parallel tests cannot run on multiple CPUs without ordering.

B Because parallel tests always run slower if ordered incorrectly.

C Because tests may share state or resources, causing failures if run simultaneously without order.

D Because test order affects the syntax of test code.

💡 Hint

Think about what happens if two tests change the same file or database at the same time.

Tests that share resources or state can interfere with each other if run simultaneously. Proper ordering or isolation prevents flaky failures.

❓ Predict Output

intermediate

Output of pytest with parallel tests sharing a file

Given the following pytest code where two tests write to the same file without synchronization, what is the likely outcome when run with pytest-xdist parallel execution?

PyTest

import pytest

@pytest.mark.parametrize('content', ['A', 'B'])
def test_write_file(tmp_path, content):
    file = tmp_path / 'shared.txt'
    with open(file, 'a') as f:
        f.write(content)
    with open(file) as f:
        data = f.read()
    assert content in data

A Tests will run sequentially ignoring parallel execution.

B Tests will always pass because each test writes different content.

C Tests will raise a SyntaxError due to invalid file operations.

D Tests may fail intermittently due to race conditions writing to the same file.

💡 Hint

Consider what happens if two tests append to the same file at the same time.

Appending to the same file concurrently can cause race conditions, leading to unpredictable file content and test failures.

❓ assertion

advanced

Correct assertion to verify test isolation in parallel runs

Which assertion best verifies that a test run in parallel does not affect the shared resource state?

PyTest

def test_resource_isolation(shared_resource):
    # shared_resource is reset before each test
    shared_resource.modify('test')
    # What assertion ensures isolation?

A assert shared_resource.state == 'initial'

B assert shared_resource.state == 'test'

C assert shared_resource is None

D assert shared_resource.state != 'initial'

💡 Hint

Isolation means the resource state should be fresh at test start.

To confirm isolation, the resource state should be the initial state before modification, ensuring no leftover changes from other tests.

🔧 Debug

advanced

Identify the cause of flaky tests in parallel pytest runs

Given this pytest code snippet, tests sometimes fail when run with pytest-xdist. What is the most likely cause?

PyTest

import pytest

shared_counter = 0

def increment():
    global shared_counter
    temp = shared_counter
    temp += 1
    shared_counter = temp

@pytest.mark.parametrize('n', range(5))
def test_increment(n):
    increment()
    assert shared_counter >= n + 1

A Incorrect assertion logic causing always failing tests.

B Race condition on shared_counter causing inconsistent increments.

C Syntax error in the increment function.

D pytest-xdist disables global variables automatically.

💡 Hint

Think about what happens when multiple tests update the same variable at the same time.

Multiple tests incrementing a shared variable without locks cause race conditions, leading to flaky test results.

❓ framework

expert

Best pytest fixture scope for parallel test isolation

Which pytest fixture scope ensures each parallel test worker gets its own fresh resource instance, preventing cross-test interference?

A scope='function'

B scope='module'

C scope='session'

D scope='package'

💡 Hint

Consider which scope creates a new fixture instance for every test function.

The 'function' scope creates a new fixture instance for each test function, ensuring isolation in parallel runs. Other scopes share instances across multiple tests, risking interference.

Practice

1. Why is it important to order tests when running pytest in parallel?

easy

A. To make tests run slower

B. To avoid conflicts when tests share resources

C. To increase the number of tests

D. To skip tests automatically

Solution

1. Step 1: Understand test resource sharing

   Tests that share resources like files or databases can interfere with each other if run at the same time.

2. Step 2: Recognize the role of ordering

   Ordering tests ensures they run in a sequence that prevents conflicts and errors.

3. Final Answer:

   To avoid conflicts when tests share resources -> Option B

4. Quick Check:

   Ordering prevents resource conflicts [OK]

Hint: Order tests to prevent shared resource conflicts [OK]

Common Mistakes:

• Thinking ordering slows tests down
• Believing ordering increases test count
• Assuming ordering skips tests

2. Which of the following is the correct way to order a test to run third using pytest?

easy

A. @pytest.mark.order(3)

B. @pytest.order(3)

C. @pytest.mark.run(3)

D. @pytest.order_mark(3)

Solution

1. Step 1: Recall pytest ordering syntax

   The correct decorator to order tests is @pytest.mark.order(n) where n is the order number.

2. Step 2: Match the syntax to options

   Only @pytest.mark.order(3) uses the correct decorator @pytest.mark.order(3).

3. Final Answer:

   @pytest.mark.order(3) -> Option A

4. Quick Check:

   Use @pytest.mark.order(n) for ordering [OK]

Hint: Use @pytest.mark.order(n) to set test order [OK]

Common Mistakes:

• Using @pytest.order instead of @pytest.mark.order
• Confusing order with run decorators
• Misspelling the decorator name

3. Given these two tests, what will be the order of execution when run with pytest in parallel with ordering?

import pytest

@pytest.mark.order(2)
def test_second():
    assert True

@pytest.mark.order(1)
def test_first():
    assert True

medium

A. Tests run in random order

B. test_second runs before test_first

C. test_first runs before test_second

D. Tests fail due to ordering conflict

Solution

1. Step 1: Identify order markers

   test_first has order 1, test_second has order 2.

2. Step 2: Understand execution order

   Lower order numbers run before higher ones, so test_first runs before test_second.

3. Final Answer:

   test_first runs before test_second -> Option C

4. Quick Check:

   Lower order number runs first [OK]

Hint: Lower order number runs first in pytest [OK]

Common Mistakes:

• Assuming higher order runs first
• Thinking tests run randomly despite order
• Believing ordering causes test failure

4. You have two tests that share a database. You want to run them in parallel safely. Which of these is a problem in the code below?

import pytest

@pytest.mark.order(1)
def test_write_db():
    # writes data
    assert True

@pytest.mark.order(2)
def test_read_db():
    # reads data
    assert True

medium

A. Tests must have the same order number

B. The order decorators are incorrect syntax

C. Tests are missing assert statements

D. Tests are ordered but may still run in parallel causing conflicts

Solution

1. Step 1: Check ordering usage

   Tests use correct order decorators, so syntax is fine.

2. Step 2: Understand parallel execution impact

   Even with order, if tests run truly in parallel (e.g., with pytest-xdist), they may overlap and cause conflicts.

3. Final Answer:

   Tests are ordered but may still run in parallel causing conflicts -> Option D

4. Quick Check:

   Ordering alone doesn't guarantee parallel safety [OK]

Hint: Ordering doesn't prevent parallel overlap without locks [OK]

Common Mistakes:

• Thinking order decorators fix parallel conflicts
• Believing same order number is required
• Ignoring assert statements importance

5. You have three tests that modify a shared file. To run them safely in parallel, you want to order them and ensure no overlap. Which approach below best achieves this?

hard

A. Use @pytest.mark.order to run tests sequentially and add file locks

B. Remove order decorators and run all tests in parallel without locks

C. Use @pytest.mark.order with the same order number for all tests

D. Run tests without ordering but add random sleep delays

Solution

1. Step 1: Understand test resource sharing

   Tests modifying the same file can cause conflicts if run simultaneously.

2. Step 2: Combine ordering with locking

   Ordering ensures sequence, and file locks prevent overlap during execution.

3. Step 3: Evaluate options

   Use @pytest.mark.order to run tests sequentially and add file locks uses both ordering and locks, which is the safest approach.

4. Final Answer:

   Use @pytest.mark.order to run tests sequentially and add file locks -> Option A

5. Quick Check:

   Order plus locks ensure parallel safety [OK]

Hint: Combine order and locks for safe parallel file tests [OK]

Common Mistakes:

• Relying on order alone without locks
• Using same order number causing race conditions
• Adding random delays instead of proper synchronization