Factory Boy for test data in Django - Step-by-Step Execution

Concept Flow - Factory Boy for test data

Define Factory Class

↓

Set Attributes & Defaults

↓

Call Factory to Create Instance

↓

Factory Builds Model Instance

↓

Instance Ready for Test Use

Factory Boy creates test data by defining factory classes with default attributes, then builds model instances when called.

Execution Sample

Django

import factory
from myapp.models import User

class UserFactory(factory.django.DjangoModelFactory):
    class Meta:
        model = User
    username = factory.Faker('user_name')

user = UserFactory()

Defines a UserFactory to create User model instances with fake usernames for tests.

Execution Table

Step	Action	Evaluation	Result
1	Define UserFactory class	Class created with Meta model User	Factory ready to build User instances
2	Set username attribute	Uses Faker to generate username	username attribute set to fake value
3	Call UserFactory()	Triggers factory build	New User instance created with fake username
4	User instance returned	Instance has username attribute	Instance ready for test use
5	End	No more actions	Factory usage complete

💡 Factory call completes after creating and returning the model instance

Variable Tracker

Variable	Start	After Step 3	Final
UserFactory	Class defined	Callable factory	Callable factory
user	Undefined	User instance with fake username	User instance with fake username

Key Moments - 2 Insights

Why does calling UserFactory() create a User instance instead of just returning the factory?

Calling UserFactory() triggers the factory's build process, which creates and returns a new User model instance as shown in execution_table step 3.

How does the username get a fake value automatically?

The username attribute uses factory.Faker('user_name'), so when the factory builds the instance, Faker generates a realistic fake username (see execution_table step 2).

Visual Quiz - 3 Questions

Look at the execution table, what is the result after step 3?

A A new User instance with a fake username is created

B The factory class is deleted

C No instance is created yet

D The username attribute is empty

💡 Hint

Check the 'Result' column in step 3 of the execution_table

At which step does the factory set the username attribute using Faker?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'Evaluation' columns in step 2 of the execution_table

If you call UserFactory() twice, what changes in variable_tracker for 'user'?

A It remains the same instance

B It becomes undefined

C It holds a new User instance each time

D It throws an error

💡 Hint

Factory creates a new instance on each call, so variable 'user' changes to a new instance

Concept Snapshot

Factory Boy creates test data by defining factory classes linked to models.
Set default or fake attributes inside the factory.
Calling the factory builds and returns a model instance.
Use Faker for realistic fake data.
Great for clean, reusable test data setup.

Full Transcript

Factory Boy helps create test data in Django by defining factory classes for models. You write a factory class with a Meta inner class pointing to your model. Inside, you set attributes, often using Faker to generate fake data. When you call the factory, it builds and returns a new model instance with those attributes. This lets you quickly create realistic test data without manually writing it each time. The execution flow starts with defining the factory, setting attributes, calling the factory to build, and finally getting the instance ready for tests.