Fixture factories in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a fixture factory in pytest?

A fixture factory is a function that returns a pytest fixture. It allows creating fixtures dynamically with parameters, helping to reuse setup code with different data.

intermediate

How do you create a fixture factory in pytest?

Define a regular function that returns a fixture function. Use @pytest.fixture inside the factory or return a nested function decorated with @pytest.fixture to generate fixtures dynamically.

beginner

Why use fixture factories instead of regular fixtures?

Fixture factories let you create multiple fixtures with different parameters without repeating code. This makes tests cleaner and easier to maintain.

intermediate

Example: How to write a fixture factory that creates user objects with different names?

import pytest

def user_factory(name):
    @pytest.fixture
    def _user():
        return {'name': name}
    return _user

Use by calling user_factory('Alice') to get a fixture for user named Alice.

intermediate

What is the benefit of using fixture factories for parameterized tests?

Fixture factories allow creating fixtures with different parameters easily, which helps run the same test logic with varied data without duplicating fixtures.

What does a fixture factory in pytest return?

A A fixture function

B A test case

C A test report

D A test runner

A fixture factory returns a fixture function that pytest can use to set up test data or state.

Why use fixture factories instead of multiple similar fixtures?

A To reduce code duplication and improve reuse

B To slow down test execution

C To make tests harder to read

D To avoid using pytest

Fixture factories help reduce repeated code by generating fixtures dynamically with different parameters.

Which decorator is used to mark a fixture in pytest?

A @pytest.run

B @pytest.fixture

C @pytest.test

D @pytest.assert

The @pytest.fixture decorator marks a function as a fixture in pytest.

How can you pass parameters to a fixture created by a fixture factory?

A By modifying pytest.ini

B By using global variables

C By calling the factory function with arguments

D By using command line options only

You pass parameters by calling the fixture factory function with arguments to create customized fixtures.

What is a common use case for fixture factories?

A Installing pytest plugins

B Running tests in parallel

C Generating test reports

D Creating test data objects with different attributes

Fixture factories are often used to create test data objects with varying attributes for flexible testing.

Explain how fixture factories improve test code reuse in pytest.

Think about how you can create many similar fixtures without writing each one separately.

Describe the steps to create and use a fixture factory in pytest with an example.

Consider a simple example like creating user objects with different names.

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