Factory Boy for test data in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Factory class from factory_boy.

Django

from factory import [1]

Drag options to blanks, or click blank then click option'

ABaseFactory

BModelFactory

CFactory

DTestFactory

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ModelFactory' which is not the base class.

Trying to import from 'factory_boy' instead of 'factory'.

The main class to create factories in Factory Boy is Factory. You import it directly from factory.

2fill in blank

medium

Complete the code to define a factory for a Django model named Book.

Django

class BookFactory([1]):
    class Meta:
        model = Book

Drag options to blanks, or click blank then click option'

ADjangoModelFactory

BFactory

CModelFactory

DBaseFactory

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Factory' which is too generic for Django models.

Using 'ModelFactory' which does not exist.

For Django models, Factory Boy provides DjangoModelFactory as the base class to handle Django-specific features.

3fill in blank

hard

Fix the error in the factory field definition to generate a sequence of titles.

Django

title = factory.[1](lambda n: f"Book {n}")

Drag options to blanks, or click blank then click option'

ALazyAttribute

BFaker

CSubFactory

DSequence

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'LazyAttribute' which does not provide a sequence number.

Using 'Faker' which generates random data, not sequences.

The Sequence field generates unique values by passing an increasing number to the lambda function.

4fill in blank

hard

Fill both blanks to create a factory field that uses Faker to generate an author name.

Django

author = factory.[1]('name')

Drag options to blanks, or click blank then click option'

ALazyFunction

BFaker

Cfaker

Dlazy_attribute

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'lazy_attribute' which is not a submodule of factory.

Using 'LazyFunction' which is unrelated here.

The correct syntax is factory.Faker('name') to generate fake author names.

5fill in blank

hard

Fill all three blanks to define a factory with a post-generation hook that adds tags to a book instance.

Django

class BookFactory(factory.[1]):
    class Meta:
        model = Book

    @factory.[2]
    def add_tags(self, create, extracted, [3]):
        if not create:
            return
        if extracted:
            for tag in extracted:
                self.tags.add(tag)

Drag options to blanks, or click blank then click option'

ADjangoModelFactory

Bpost_generation

Cself

DLazyAttribute

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Factory' instead of 'DjangoModelFactory' for the base class.

Using 'post_generation' as a method name instead of a decorator.

Naming the instance parameter something other than 'self'.

The factory class should inherit from DjangoModelFactory. The decorator for post-generation hooks is post_generation. The method parameter for the instance is conventionally named self.

Practice

1. What is the main purpose of using Factory Boy in Django testing?

easy

A. To create reusable fake data for tests easily

B. To speed up the Django server

C. To replace Django's ORM

D. To deploy Django applications automatically

Solution

1. Step 1: Understand Factory Boy's role

   Factory Boy is designed to generate fake data for tests, making test setup easier and less repetitive.

2. Step 2: Eliminate unrelated options

   Speeding up the server, replacing ORM, or deployment are unrelated to test data creation.

3. Final Answer:

   To create reusable fake data for tests easily -> Option A

4. Quick Check:

   Factory Boy = reusable fake test data [OK]

Hint: Factory Boy = fake test data creator [OK]

Common Mistakes:

• Thinking Factory Boy speeds up the server
• Confusing Factory Boy with deployment tools
• Assuming Factory Boy replaces Django ORM

2. Which of the following is the correct way to define a basic factory for a Django model Book using Factory Boy?

easy

A. class BookFactory(factory.DjangoModelFactory): class Meta: model = Book

B. class BookFactory(factory.Factory): model = Book

C. class BookFactory(factory.ModelFactory): model = Book

D. class BookFactory(factory.DjangoFactory): class Meta: model = Book

Solution

1. Step 1: Identify correct base class

   Factory Boy uses DjangoModelFactory as the base class for Django models.

2. Step 2: Check Meta class usage

   The model must be specified inside a nested Meta class with attribute model.

3. Final Answer:

   class BookFactory(factory.DjangoModelFactory): class Meta: model = Book -> Option A

4. Quick Check:

   DjangoModelFactory + Meta.model = correct syntax [OK]

Hint: Use DjangoModelFactory with Meta.model for Django models [OK]

Common Mistakes:

• Using factory.Factory instead of DjangoModelFactory
• Not using a Meta class for model assignment
• Using incorrect base class names

3. Given this factory definition:

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

What will UserFactory().username return?

medium

A. None, because username is not set

B. The literal string 'user_name'

C. An error because Faker is not imported

D. A random username string generated by Faker

Solution

1. Step 1: Understand Faker usage in Factory Boy

   Using factory.Faker('user_name') generates a random username string each time the factory is called.

2. Step 2: Evaluate the expression UserFactory().username

   Calling UserFactory() creates a User instance with a random username, so .username returns that random string.

3. Final Answer:

   A random username string generated by Faker -> Option D

4. Quick Check:

   Faker('user_name') = random username string [OK]

Hint: Faker fields produce random data, not literals [OK]

Common Mistakes:

• Thinking Faker returns the field name as string
• Assuming missing imports cause runtime error here
• Expecting None if not explicitly set

4. What is wrong with this factory code?

class ProductFactory(factory.DjangoModelFactory):
    class Meta:
        model = Product
    name = factory.Faker('product_name')
    price = factory.Faker('float')

medium

A. Faker does not have a 'product_name' provider

B. The 'float' provider requires arguments to specify range

C. Missing import of factory module

D. Meta class should be outside the factory class

Solution

1. Step 1: Check Faker providers used

   Faker has no built-in 'product_name' provider, but this is a common custom name; however, 'float' requires arguments like min and max.

2. Step 2: Identify the error cause

   Using factory.Faker('float') without arguments causes an error because Faker's float provider needs parameters.

3. Final Answer:

   The 'float' provider requires arguments to specify range -> Option B

4. Quick Check:

   Faker float needs min/max args [OK]

Hint: Faker float needs range arguments to work [OK]

Common Mistakes:

• Assuming 'product_name' is always valid
• Ignoring required arguments for Faker float
• Thinking Meta class placement is wrong

5. You want to create a factory for a Django model Order that has a foreign key to User. How do you correctly define the user field in OrderFactory to use UserFactory?

hard

A. user = UserFactory()

B. user = factory.RelatedFactory(UserFactory)

C. user = factory.SubFactory(UserFactory)

D. user = factory.Faker('user')

Solution

1. Step 1: Understand foreign key factory usage

   To link a foreign key to another factory, use factory.SubFactory with the related factory class.

2. Step 2: Evaluate options

   Directly calling UserFactory() assigns an instance at class load time, not per object. RelatedFactory is for reverse relations. Faker does not create model instances.

3. Final Answer:

   user = factory.SubFactory(UserFactory) -> Option C

4. Quick Check:

   Foreign key uses SubFactory [OK]

Hint: Use SubFactory for foreign key relations [OK]

Common Mistakes:

• Calling UserFactory() directly in factory field
• Using RelatedFactory for foreign keys
• Using Faker for model relations