Fixture dependencies (fixture using fixture) in PyTest - Framework Patterns

Framework Mode - Fixture dependencies (fixture using fixture)

Folder Structure

project-root/
├── tests/
│   ├── test_example.py
│   └── conftest.py
├── src/
│   └── app_code.py
├── pytest.ini
└── requirements.txt
  

Test Framework Layers

• Fixtures Layer: Defined in conftest.py, fixtures can depend on other fixtures to share setup logic.
• Test Layer: Test files in tests/ use fixtures by declaring them as function parameters.
• Application Code Layer: The src/ folder contains the main application code under test.
• Configuration Layer: pytest.ini holds pytest configuration options.

Configuration Patterns

Use pytest.ini or tox.ini to configure pytest options like markers and test paths.

Manage environment variables or secrets outside code, e.g., with .env files or CI environment settings.

Fixtures can accept parameters or use pytest_addoption to handle different environments or browsers.

Test Reporting and CI/CD Integration

• Use pytest plugins like pytest-html or pytest-cov for HTML reports and coverage.
• Integrate pytest runs in CI pipelines (GitHub Actions, Jenkins) with commands like pytest --junitxml=report.xml.
• Reports help track test results and fixture setup success or failures.

Best Practices

1. Keep fixtures small and focused: Each fixture should do one setup task.
2. Use fixture dependencies: Let fixtures use other fixtures to avoid repeating setup code.
3. Scope fixtures appropriately: Use function, module, or session scopes to optimize test speed.
4. Use autouse sparingly: Only when you want fixtures to run automatically without explicit use.
5. Document fixtures: Add docstrings so others understand what each fixture provides.

Self Check

Where in this folder structure would you add a new fixture that depends on an existing database connection fixture?

Key Result

Use pytest fixtures with dependencies defined in conftest.py to share setup logic cleanly across tests.

Practice

1. What happens when a pytest fixture uses another fixture as a parameter?

easy

A. pytest runs both fixtures in parallel without passing results

B. pytest ignores the dependent fixture and runs only the main fixture

C. pytest runs the dependent fixture first and passes its result automatically

D. pytest throws a syntax error because fixtures cannot use other fixtures

Solution

1. Step 1: Understand fixture dependency in pytest

   When a fixture uses another fixture as a parameter, pytest recognizes this dependency and runs the dependent fixture first.

2. Step 2: How pytest passes results between fixtures

   pytest automatically passes the result of the dependent fixture to the main fixture as an argument.

3. Final Answer:

   pytest runs the dependent fixture first and passes its result automatically -> Option C

4. Quick Check:

   Fixture dependency means automatic result passing [OK]

Hint: Dependent fixtures run first and pass results automatically [OK]

Common Mistakes:

• Thinking fixtures run independently without passing results
• Believing fixture dependencies cause errors
• Assuming fixtures run in parallel without order

2. Which of the following is the correct syntax to use one fixture inside another in pytest?

easy

A. @pytest.fixture
def fixture_a():
return 5

@pytest.fixture
def fixture_b(fixture_a):
return fixture_a + 3

B. @pytest.fixture
def fixture_a():
return 5

@pytest.fixture
def fixture_b():
fixture_a + 3

C. @pytest.fixture
def fixture_a():
return 5

@pytest.fixture
def fixture_b():
return fixture_a() + 3

D. @pytest.fixture
def fixture_a():
return 5

@pytest.fixture
def fixture_b():
return 3 + 5

Solution

1. Step 1: Check how fixtures receive other fixtures

   Fixtures use other fixtures by naming them as parameters in the function definition.

2. Step 2: Validate the syntax of fixture_b

   @pytest.fixture def fixture_a(): return 5 @pytest.fixture def fixture_b(fixture_a): return fixture_a + 3 correctly defines fixture_b with fixture_a as a parameter, allowing pytest to inject fixture_a's return value.

3. Final Answer:

   @pytest.fixture def fixture_b(fixture_a): return fixture_a + 3 -> Option A

4. Quick Check:

   Fixture as parameter = correct syntax [OK]

Hint: Use fixture names as parameters to depend on them [OK]

Common Mistakes:

• Calling fixture functions directly inside another fixture
• Not passing dependent fixture as parameter
• Trying to use fixture variables without parameters

3. Given the code below, what will be the output when running the test?

import pytest

@pytest.fixture
def base():
    return 10

@pytest.fixture
def add_five(base):
    return base + 5

def test_sum(add_five):
    assert add_five == 15
    print(add_five)

medium

A. 5

B. 10

C. AssertionError

D. 15

Solution

1. Step 1: Understand fixture dependency and values

   The fixture 'base' returns 10. The fixture 'add_five' uses 'base' and returns 10 + 5 = 15.

2. Step 2: Analyze the test function output

   The test asserts that 'add_five' equals 15, which is true, then prints 15.

3. Final Answer:

   15 -> Option D

4. Quick Check:

   Dependent fixture value = 15 [OK]

Hint: Dependent fixture returns combined value, test prints it [OK]

Common Mistakes:

• Confusing fixture return values
• Expecting base value instead of combined
• Assuming print outputs test result

4. Identify the error in the following pytest fixture code:

import pytest

@pytest.fixture
def data():
    return [1, 2, 3]

@pytest.fixture
def processed_data():
    data.append(4)
    return data

medium

A. 'data' fixture returns a tuple, but 'processed_data' expects a list

B. 'data' fixture is not passed as a parameter to 'processed_data' fixture

C. 'processed_data' fixture is missing the @pytest.mark decorator

D. 'data' fixture is called inside 'processed_data' without parentheses

Solution

1. Step 1: Check how 'processed_data' accesses 'data'

   'processed_data' tries to use 'data' but does not receive it as a parameter, so 'data' is undefined in its scope.

2. Step 2: Correct way to use fixture dependencies

   To use one fixture inside another, the dependent fixture must be listed as a parameter in the function definition.

3. Final Answer:

   'data' fixture is not passed as a parameter to 'processed_data' fixture -> Option B

4. Quick Check:

   Fixture dependency requires parameter passing [OK]

Hint: Always pass dependent fixtures as parameters [OK]

Common Mistakes:

• Using fixture names without parameters
• Calling fixture functions directly inside another fixture
• Missing @pytest.fixture decorator

5. You want to create a pytest fixture full_config that depends on two other fixtures: base_config returning a dict {'host': 'localhost'} and auth_config returning {'user': 'admin'}. Which code correctly combines these fixtures so full_config returns {'host': 'localhost', 'user': 'admin'}?

hard

A. @pytest.fixture
def base_config():
return {'host': 'localhost'}

@pytest.fixture
def auth_config():
return {'user': 'admin'}

@pytest.fixture
def full_config(base_config, auth_config):
return {**base_config, **auth_config}

B. @pytest.fixture
def base_config():
return {'host': 'localhost'}

@pytest.fixture
def auth_config():
return {'user': 'admin'}

@pytest.fixture
def full_config():
return {**base_config(), **auth_config()}

C. @pytest.fixture
def base_config():
return {'host': 'localhost'}

@pytest.fixture
def auth_config():
return {'user': 'admin'}

@pytest.fixture
def full_config():
return base_config + auth_config

D. @pytest.fixture
def base_config():
return {'host': 'localhost'}

@pytest.fixture
def auth_config():
return {'user': 'admin'}

@pytest.fixture
def full_config(base_config):
return base_config.update(auth_config())

Solution

1. Step 1: Understand fixture dependencies and parameter passing

   To combine two fixtures, the dependent fixture must list both as parameters to receive their return values.

2. Step 2: Combine dictionaries correctly

   Using {**dict1, **dict2} merges two dictionaries into one. @pytest.fixture def base_config(): return {'host': 'localhost'} @pytest.fixture def auth_config(): return {'user': 'admin'} @pytest.fixture def full_config(base_config, auth_config): return {**base_config, **auth_config} correctly does this with both fixtures as parameters.

3. Final Answer:

   @pytest.fixture def full_config(base_config, auth_config): return {**base_config, **auth_config} -> Option A

4. Quick Check:

   Pass fixtures as parameters and merge dicts [OK]

Hint: Pass all fixtures as parameters and merge dicts with ** [OK]

Common Mistakes:

• Calling fixture functions directly instead of passing as parameters
• Trying to add dictionaries with + operator
• Using dict.update() which returns null