Avoiding test interdependence in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why avoid test interdependence?

In pytest, why is it important to avoid test interdependence?

A Because dependent tests can cause false failures if one test fails, affecting others.

B Because pytest does not allow tests to share any data or fixtures.

C Because interdependent tests run slower than independent tests.

D Because tests that depend on each other cannot be run in parallel.

💡 Hint

Think about what happens if one test fails and others rely on it.

Tests that depend on each other can cause cascading failures, making it hard to find the real problem. Independent tests help isolate issues.

❓ Predict Output

intermediate

Output of pytest with interdependent tests

What will be the output status of the second test when running pytest on this code?

PyTest

shared_list = []

def test_add_item():
    shared_list.append(1)
    assert len(shared_list) == 1

def test_check_item():
    assert shared_list == [1]

A First test fails, second test passes

B First test passes, second test fails

C Both tests pass

D Both tests fail

💡 Hint

Consider the order pytest runs tests and the shared state.

Because test_add_item runs first and adds 1 to shared_list, test_check_item sees [1] and passes. But this creates interdependence on test order.

❓ assertion

advanced

Correct assertion to avoid interdependence

Which assertion best avoids test interdependence by ensuring each test starts with a clean state?

PyTest

import pytest

@pytest.fixture(autouse=True)
def clear_list():
    global shared_list
    shared_list = []

shared_list = []

def test_one():
    shared_list.append(5)
    # Assertion here

def test_two():
    # Assertion here

A assert shared_list == [5] in test_one and assert shared_list == [] in test_two

B assert len(shared_list) == 0 in both tests

C assert shared_list == [5] in both tests

D assert len(shared_list) > 0 in both tests

💡 Hint

Think about what the fixture does before each test.

The fixture resets shared_list to empty before each test. test_one adds 5, so it expects [5]. test_two expects empty list because fixture cleared it.

🔧 Debug

advanced

Identify the cause of test interdependence

Given these pytest tests, why might test_b fail if run alone?

PyTest

shared_counter = 0

def test_a():
    global shared_counter
    shared_counter += 1
    assert shared_counter == 1

def test_b():
    assert shared_counter == 1

A Because shared_counter is reset to 0 before each test automatically.

B Because test_b depends on test_a to run first and modify shared_counter.

C Because test_b modifies shared_counter before asserting.

D Because pytest runs tests in parallel causing race conditions.

💡 Hint

Think about the initial value of shared_counter and test order.

test_b expects shared_counter to be 1, but if run alone, shared_counter is 0. This shows test_b depends on test_a's side effect.

❓ framework

expert

Best pytest practice to avoid test interdependence

Which pytest feature is best to ensure tests do not share state and remain independent?

A Running tests in a fixed order to maintain state consistency

B Using global variables to share data between tests

C Disabling pytest's test isolation features for faster runs

D Using fixtures with scope='function' to provide fresh data for each test

💡 Hint

Think about how pytest can reset or provide fresh data for each test.

Fixtures with function scope run before each test, giving a clean state and avoiding interdependence. Global variables and fixed order cause dependencies.