Testing models in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Django model test?

Consider this Django model test code. What will be the output when running this test?

Django

from django.test import TestCase
from myapp.models import Product

class ProductTest(TestCase):
    def test_str_method(self):
        product = Product(name='Book', price=10)
        self.assertEqual(str(product), 'Book')

A Test passes successfully

B Test fails with AssertionError

C Raises AttributeError because price is missing

D Raises TypeError due to wrong argument

💡 Hint

Check what the __str__ method of the Product model returns.

The test creates a Product instance with name 'Book' and price 10. The test checks if str(product) returns 'Book'. If the Product model's __str__ method returns the name, the test passes.

❓ state_output

intermediate

What is the value of product_count after test?

Given this Django test case, what is the value of product_count after running test_product_creation?

Django

from django.test import TestCase
from myapp.models import Product

class ProductTest(TestCase):
    def test_product_creation(self):
        Product.objects.create(name='Pen', price=5)
        Product.objects.create(name='Pencil', price=3)
        product_count = Product.objects.count()

A 2

B 0

C 1

D Raises DatabaseError

💡 Hint

Count how many Product objects are created in the test.

Two Product objects are created in the test, so the count is 2.

🔧 Debug

advanced

What error does this Django model test raise?

This test tries to create a Product without a required field. What error will it raise?

Django

from django.test import TestCase
from myapp.models import Product

class ProductTest(TestCase):
    def test_missing_name(self):
        Product.objects.create(price=10)

A No error, object created

B ValueError

C TypeError

D django.db.utils.IntegrityError

💡 Hint

Check if the name field is required and what happens if it is missing.

If the name field is required (not nullable), the database will raise IntegrityError when trying to insert a null value.

📝 Syntax

advanced

Which option fixes the syntax error in this Django test?

Identify the correct syntax to define a Django test method inside a TestCase class.

Django

from django.test import TestCase

class ProductTest(TestCase):
    def test_product(self)
        self.assertTrue(True)

A

def test_product(self):
self.assertTrue(True)

B

def test_product(self):
    self.assertTrue(True)

C

def test_product():
    self.assertTrue(True)

D

def test_product(self):
    assertTrue(True)

💡 Hint

Check for missing colon and indentation.

Option B correctly adds the missing colon and proper indentation for the method body.

🧠 Conceptual

expert

Which option best describes Django's test database behavior?

When running Django model tests, what happens to the test database after tests complete?

A The test database is created once and reused for all test runs without deletion

B The test database is the same as the development database and is not deleted

C The test database is created before tests and destroyed after tests finish

D The test database is created after tests finish

💡 Hint

Think about how Django isolates tests from your real data.

Django creates a separate test database before tests run and deletes it after tests finish to keep tests isolated.

Practice

1. What is the main purpose of testing Django models?

easy

A. To ensure the data logic and model methods work correctly

B. To improve the website's visual design

C. To speed up the server response time

D. To create user interface components

Solution

1. Step 1: Understand the role of models in Django

   Models define data structure and logic in Django applications.

2. Step 2: Identify the goal of testing models

   Testing models ensures that data saving, retrieval, and custom methods behave as expected.

3. Final Answer:

   To ensure the data logic and model methods work correctly -> Option A

4. Quick Check:

   Testing models = data logic correctness [OK]

Hint: Models hold data logic; tests check if it works right [OK]

Common Mistakes:

• Confusing model testing with UI testing
• Thinking model tests improve site speed
• Assuming model tests create frontend components

2. Which of the following is the correct way to start a test method in a Django TestCase class?

easy

A. def check_model(self):

B. def test_model(self):

C. def model_test(self):

D. def testing_model(self):

Solution

1. Step 1: Recall Django test method naming conventions

   Django runs test methods only if their names start with test_.

2. Step 2: Match the method name to the convention

   Only def test_model(self): starts with test_, so it will be executed as a test.

3. Final Answer:

   def test_model(self): -> Option B

4. Quick Check:

   Test methods start with 'test_' [OK]

Hint: Test methods must start with 'test_' to run [OK]

Common Mistakes:

• Using method names without 'test_' prefix
• Assuming any method in TestCase runs as test
• Confusing test method naming with variable names

3. Given this Django model and test code, what will be the output of the test?

class Product(models.Model):
    name = models.CharField(max_length=100)
    def __str__(self):
        return self.name

class ProductTest(TestCase):
    def test_str_method(self):
        p = Product(name='Book')
        self.assertEqual(str(p), 'Book')

medium

A. Test passes successfully

B. Test fails with AssertionError

C. Test raises a TypeError

D. Test raises a ValueError

Solution

1. Step 1: Understand the __str__ method in Product model

   The __str__ method returns the product's name string.

2. Step 2: Analyze the test code behavior

   The test creates a Product instance with name 'Book' and checks if str(p) equals 'Book'. Since __str__ returns name, this is true.

3. Final Answer:

   Test passes successfully -> Option A

4. Quick Check:

   __str__ returns name, so test passes [OK]

Hint: Check __str__ returns expected string for test pass [OK]

Common Mistakes:

• Forgetting to save the model instance before testing
• Assuming __str__ returns something else
• Confusing test failure with error

4. Identify the error in this Django model test code:

class UserProfile(models.Model):
    age = models.IntegerField()

class UserProfileTest(TestCase):
    def test_age_positive(self):
        profile = UserProfile(age=-5)
        self.assertTrue(profile.age > 0)

medium

A. The model field type is incorrect for age

B. The test method name does not start with 'test_'

C. The test will fail because age is negative but no validation is done

D. The test should use assertFalse instead of assertTrue

Solution

1. Step 1: Review the test logic

   The test creates a UserProfile with age -5 and asserts age > 0, which is false.

2. Step 2: Identify why the test fails

   There is no validation preventing negative age, so the test fails as expected.

3. Final Answer:

   The test will fail because age is negative but no validation is done -> Option C

4. Quick Check:

   Negative age without validation causes test failure [OK]

Hint: Check test logic matches model validation to avoid failure [OK]

Common Mistakes:

• Assuming test method name is wrong
• Thinking IntegerField rejects negatives by default
• Confusing assertTrue with assertFalse usage

5. You want to test a custom model method that returns the full name by combining first and last names. Which approach correctly tests this method?

class Person(models.Model):
    first_name = models.CharField(max_length=30)
    last_name = models.CharField(max_length=30)
    def full_name(self):
        return f"{self.first_name} {self.last_name}"

# Test code?

hard

A. Use assertEqual on first_name and last_name separately

B. Only check if first_name and last_name fields exist in the model

C. Test full_name() without creating a Person instance

D. Create a Person instance, call full_name(), and assert the combined string

Solution

1. Step 1: Understand what the full_name method does

   It returns a string combining first_name and last_name with a space.

2. Step 2: Determine how to test this method

   Create a Person instance with known names, call full_name(), and check if the result matches the expected combined string.

3. Final Answer:

   Create a Person instance, call full_name(), and assert the combined string -> Option D

4. Quick Check:

   Test custom method by calling it on instance and checking output [OK]

Hint: Test custom methods by calling them on model instances [OK]

Common Mistakes:

• Testing fields instead of method output
• Calling method without instance
• Checking fields separately instead of combined result