Avoiding test interdependence in PyTest - Build an Automation Script

Verify independent test execution in pytest

Preconditions (2)

Step 1: Create two test functions: test_add and test_subtract

Step 2: In test_add, call add(2, 3) and verify the result is 5

Step 3: In test_subtract, call subtract(5, 3) and verify the result is 2

Step 4: Run tests individually and together to ensure no test depends on another

✅ Expected Result: Both tests pass independently with no shared state or order dependency

Automation Requirements - pytest

Assertions Needed:

assert add(2, 3) == 5

assert subtract(5, 3) == 2

Best Practices:

Use fresh state for each test

Avoid sharing variables or state between tests

Do not rely on test execution order

Use fixtures with scope='function' if setup is needed

Automated Solution

PyTest

import pytest

# Simple calculator functions
def add(a, b):
    return a + b

def subtract(a, b):
    return a - b

# Test functions

def test_add():
    result = add(2, 3)
    assert result == 5

def test_subtract():
    result = subtract(5, 3)
    assert result == 2

This test script defines two simple functions: add and subtract. Each test function calls one of these and asserts the expected result.

Each test is independent: they do not share variables or state. This means you can run test_add or test_subtract alone or together in any order, and they will pass.

This avoids test interdependence, which is important because tests that depend on each other can cause confusing failures and make debugging hard.

Common Mistakes - 3 Pitfalls

Sharing variables between tests

Relying on test execution order

Using global state without reset

Bonus Challenge

Now add data-driven testing with 3 different input pairs for add and subtract functions

Show Hint

Practice

1. Why is it important to avoid test interdependence in pytest?

easy

A. To ensure each test runs independently and results are reliable

B. To make tests run faster by sharing data

C. To reduce the number of test functions needed

D. To allow tests to modify global variables freely

Solution

1. Step 1: Understand test independence

   Tests should not rely on each other to avoid hidden bugs and unclear results.

2. Step 2: Identify the benefit of independence

   Independent tests ensure that a failure in one test does not affect others, making debugging easier.

3. Final Answer:

   To ensure each test runs independently and results are reliable -> Option A

4. Quick Check:

   Test independence = Reliable results [OK]

Hint: Tests must run alone to keep results clear and reliable [OK]

Common Mistakes:

• Thinking tests should share data to run faster
• Believing test order does not matter
• Allowing tests to modify shared global state

2. Which pytest feature helps to avoid test interdependence by preparing fresh data for each test?

easy

A. Using print statements for debugging

B. Using global variables

C. Using fixtures with scope='function'

D. Using assert statements inside tests

Solution

1. Step 1: Identify pytest features for setup

   Fixtures with scope='function' run before each test, providing fresh data.

2. Step 2: Understand why this avoids interdependence

   Fresh data per test prevents tests from affecting each other through shared state.

3. Final Answer:

   Using fixtures with scope='function' -> Option C

4. Quick Check:

   Fixtures with function scope = Fresh data each test [OK]

Hint: Use function-scoped fixtures to reset data per test [OK]

Common Mistakes:

• Using global variables which cause shared state
• Confusing print statements with setup tools
• Thinking assert statements control test independence

3. Given the following pytest code, what will be the output when running both tests?

shared_list = []

def test_add_one():
    shared_list.append(1)
    assert shared_list == [1]

def test_add_two():
    shared_list.append(2)
    assert shared_list == [2]

medium

A. Both tests pass

B. Both tests fail

C. test_add_one fails, test_add_two passes

D. test_add_one passes, test_add_two fails

Solution

1. Step 1: Analyze shared_list state across tests

   shared_list is global and not reset, so after test_add_one it contains [1].

2. Step 2: Check assertions in each test

   test_add_one expects [1] and passes; test_add_two appends 2 making list [1,2], but asserts [2], so it fails.

3. Final Answer:

   test_add_one passes, test_add_two fails -> Option D

4. Quick Check:

   Shared state causes second test failure [OK]

Hint: Global mutable state causes test failures due to leftover data [OK]

Common Mistakes:

• Assuming shared_list resets automatically
• Ignoring order of test execution
• Expecting both tests to pass with shared state

4. Identify the problem in this pytest code that causes test interdependence:

data = {}

def test_set_value():
    data['key'] = 'value'
    assert data['key'] == 'value'

def test_check_empty():
    assert data == {}

medium

A. Using dict instead of list causes errors

B. data dictionary is not reset between tests

C. Tests are missing return statements

D. Assertions are incorrect syntax

Solution

1. Step 1: Examine shared data usage

   data is a global dictionary modified in test_set_value and not cleared before test_check_empty.

2. Step 2: Understand test impact

   test_check_empty expects data to be empty, but it contains {'key': 'value'}, causing failure and interdependence.

3. Final Answer:

   data dictionary is not reset between tests -> Option B

4. Quick Check:

   Shared mutable dict causes test dependency [OK]

Hint: Reset shared data to avoid tests affecting each other [OK]

Common Mistakes:

• Thinking assertions syntax is wrong
• Believing return statements are needed in tests
• Confusing data types with test independence

5. You want to avoid test interdependence in pytest when multiple tests modify a shared database. Which approach is best?

hard

A. Use a fixture that creates a fresh database for each test and cleans up after

B. Share one database instance and reset it manually in one test only

C. Run tests in a specific order so dependencies are met

D. Use global variables to track database state across tests

Solution

1. Step 1: Understand best practice for shared resources

   Creating a fresh database per test ensures no leftover data affects other tests.

2. Step 2: Evaluate other options

   Sharing one instance with manual reset or relying on test order causes hidden dependencies and fragile tests.

3. Final Answer:

   Use a fixture that creates a fresh database for each test and cleans up after -> Option A

4. Quick Check:

   Fresh resource per test = No interdependence [OK]

Hint: Fresh setup and cleanup per test avoids hidden dependencies [OK]

Common Mistakes:

• Relying on test order which is unreliable
• Using global variables causing shared state bugs
• Resetting shared state in only one test