Factory Fixtures

Factory fixtures address two common testing challenges: improving test readability and making tests resistant to unrelated changes. These fixtures return functions to create objects rather than pre-created objects, allowing developers to set sensible defaults while overriding only relevant attributes.

The Problem Statement

When writing comprehensive tests, developers frequently encounter:

• Simple unrelated changes breaking numerous tests (like adding a required object attribute)
• Tests that are difficult to read due to extensive setup code for irrelevant attributes

Password Validation Example

Consider a User model with these password requirements:

• Minimum 8 characters
• At least one uppercase letter
• At least one lowercase letter
• At least one special character
• At least one digit

Traditional Approach Issues

Without factory fixtures, developers must recreate complete user objects in each test, including all required fields. This creates verbose, cluttered test code where only password values matter.

Factory Fixture Solution

@pytest.fixture
def user_factory():
    def create_user(
        email="test@example.com",
        password="ValidPass1!",
        name="Test User",
        is_active=True,
    ):
        return User(
            email=email,
            password=password,
            name=name,
            is_active=is_active,
        )
    return create_user


def test_password_requires_uppercase(user_factory):
    user = user_factory(password="lowercase1!")
    assert not user.is_password_valid()


def test_password_requires_digit(user_factory):
    user = user_factory(password="NoDigits!")
    assert not user.is_password_valid()

A factory fixture provides a reusable function accepting keyword arguments with sensible defaults. Tests become more concise and clearly communicate which attributes are relevant, significantly enhancing readability.

Resistance to Changes

When new attributes (like status fields) are added to models, factory-fixture-based tests require modifications only in the fixture itself, not in individual tests. This prevents cascading test failures from implementation changes.

Conclusion

Factory fixtures improve code clarity while reducing maintenance burden as projects scale.