Fixture factories in PyTest - Framework Patterns

Framework Mode - Fixture factories

Folder Structure

tests/
├── test_user.py
├── test_order.py
├── conftest.py
utils/
├── data_factories.py
├── helpers.py

Test Framework Layers

• Fixture Factories Layer: Located in utils/data_factories.py, this layer contains factory functions that create test data objects or test fixtures dynamically.
• Fixtures Layer: Defined in conftest.py, it uses fixture factories to provide reusable test data or setup for tests.
• Test Layer: Test files inside tests/ folder use fixtures to run test cases.
• Utilities Layer: Helper functions and common utilities in utils/helpers.py support test logic and data creation.

Configuration Patterns

• Environment Handling: Use environment variables or pytest.ini to select test environment (dev, staging, prod).
• Fixture Parameters: Fixture factories accept parameters to customize created data for different test scenarios.
• Credentials: Store sensitive data securely outside code, inject via fixtures or environment variables.
• Browser or External Service Config: Use pytest command line options or config files to select browsers or service endpoints.

Test Reporting and CI/CD Integration

• Use pytest built-in reporting with options like --junitxml=report.xml for CI systems.
• Integrate with CI tools (GitHub Actions, Jenkins) to run tests automatically on code changes.
• Use plugins like pytest-html for readable HTML reports.
• Ensure fixture factories produce consistent data to avoid flaky tests and improve report reliability.

Best Practices

• Keep Fixture Factories Simple: Each factory creates one type of test data object with clear parameters.
• Reuse Factories in Fixtures: Use fixture factories inside conftest.py fixtures to avoid duplication.
• Parameterize Factories: Allow customization of test data to cover multiple scenarios without rewriting code.
• Isolate Test Data: Factories should create fresh data for each test to prevent side effects.
• Document Factories: Clearly explain what data each factory produces and its parameters.

Self Check

Where in this framework structure would you add a new fixture factory for creating Product test data objects?

Key Result

Use fixture factories in a utilities layer to create reusable, customizable test data for pytest fixtures.

Practice

1. What is the main purpose of a fixture factory in pytest?

easy

A. To generate random test data without any input

B. To create reusable setup functions that can accept parameters

C. To run tests in parallel automatically

D. To replace the need for assertions in tests

Solution

1. Step 1: Understand what a fixture factory does

   A fixture factory is a fixture that returns a function, allowing parameter input to create varied setups.

2. Step 2: Compare options with this definition

   Only To create reusable setup functions that can accept parameters describes creating reusable setup functions that accept parameters, which matches the fixture factory concept.

3. Final Answer:

   To create reusable setup functions that can accept parameters -> Option B

4. Quick Check:

   Fixture factory = reusable setup with parameters [OK]

Hint: Fixture factories return functions to customize setup [OK]

Common Mistakes:

• Thinking fixture factories run tests in parallel
• Confusing fixture factories with random data generators
• Believing fixture factories remove the need for assertions

2. Which of the following is the correct syntax to define a fixture factory in pytest?

easy

A. @pytest.fixture
def data_factory():
def create_data(value):
return {'key': value}
return create_data

B. @pytest.fixture
def data_factory(value):
return {'key': value}

C. def data_factory():
return {'key': 'value'}

D. @pytest.fixture
def data_factory():
return {'key': 'value'}

Solution

1. Step 1: Identify fixture factory structure

   A fixture factory is a fixture that returns a function which accepts parameters.

2. Step 2: Check each option

   @pytest.fixture def data_factory(): def create_data(value): return {'key': value} return create_data defines a fixture returning a function that takes a parameter, matching fixture factory syntax. Others either lack the inner function or parameter handling.

3. Final Answer:

   @pytest.fixture\ndef data_factory():\n def create_data(value):\n return {'key': value}\n return create_data -> Option A

4. Quick Check:

   Fixture factory = fixture returning a function [OK]

Hint: Fixture factory returns a function inside a fixture [OK]

Common Mistakes:

• Defining fixture with parameters directly (not allowed)
• Returning data directly without inner function
• Missing @pytest.fixture decorator

3. Given the following pytest fixture factory and test, what will be the output of the assertion?

@pytest.fixture
def user_factory():
    def create_user(name):
        return {'name': name, 'active': True}
    return create_user

def test_user_active(user_factory):
    user = user_factory('Alice')
    assert user['active'] is True

medium

A. Test passes because 'active' is True

B. Test fails because 'active' key is missing

C. Test fails due to TypeError in fixture

D. Test fails because 'name' is not 'Alice'

Solution

1. Step 1: Understand fixture factory behavior

   The fixture returns a function that creates a user dict with 'name' and 'active' set to True.

2. Step 2: Analyze the test

   The test calls user_factory('Alice'), getting {'name': 'Alice', 'active': True}, then asserts user['active'] is True, which is correct.

3. Final Answer:

   Test passes because 'active' is True -> Option A

4. Quick Check:

   user['active'] = True, assertion passes [OK]

Hint: Check returned dict keys and values carefully [OK]

Common Mistakes:

• Assuming 'active' key is missing
• Confusing fixture factory return with direct dict
• Thinking 'name' must be 'Bob' instead of 'Alice'

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

@pytest.fixture
def product_factory():
    def create_product(name, price):
        return {'name': name, 'price': price}
    return create_product

def test_product(product_factory):
    product = product_factory('Book')
    assert product['price'] > 0

medium

A. Incorrect return statement in fixture factory

B. Fixture factory missing @pytest.fixture decorator

C. Missing price argument when calling product_factory in test

D. Assertion compares string to integer

Solution

1. Step 1: Check fixture factory parameters

   The inner function create_product requires two parameters: name and price.

2. Step 2: Check test call to fixture factory

   The test calls product_factory('Book') with only one argument, missing price, causing a TypeError.

3. Final Answer:

   Missing price argument when calling product_factory in test -> Option C

4. Quick Check:

   Function call missing required argument [OK]

Hint: Match all required parameters when calling fixture factory [OK]

Common Mistakes:

• Forgetting to pass all parameters to inner function
• Assuming fixture factory itself takes parameters
• Ignoring error messages about missing arguments

5. You want to test a function that processes orders with different quantities and prices. How can you use a fixture factory to create varied order data for multiple tests efficiently?

hard

A. Hardcode order data inside each test function

B. Write separate fixtures for each order variation without parameters

C. Use a global variable to store order data and modify it in tests

D. Create a fixture factory that returns a function accepting quantity and price, returning an order dict

Solution

1. Step 1: Understand the need for varied test data

   Testing different quantities and prices requires flexible data creation without repeating code.

2. Step 2: Apply fixture factory concept

   A fixture factory returning a function that accepts quantity and price allows creating varied order dicts efficiently.

3. Final Answer:

   Create a fixture factory that returns a function accepting quantity and price, returning an order dict -> Option D

4. Quick Check:

   Fixture factory = flexible, reusable test data creator [OK]

Hint: Use fixture factory to pass parameters for varied data [OK]

Common Mistakes:

• Writing many similar fixtures instead of one factory
• Using global variables causing test interference
• Hardcoding data reduces test flexibility and reuse