TestCase and SimpleTestCase in Django - Mini Project: Build & Apply

Using TestCase and SimpleTestCase in Django

📖 Scenario: You are building a Django app that needs to test some simple logic and database interactions.

🎯 Goal: Learn how to write tests using Django's SimpleTestCase for simple logic and TestCase for database-related tests.

📋 What You'll Learn

Create a simple function to test with SimpleTestCase

Create a Django model to test with TestCase

Write a SimpleTestCase class to test the simple function

Write a TestCase class to test the model's database behavior

💡 Why This Matters

🌍 Real World

Testing is essential in Django projects to ensure code works correctly and database interactions behave as expected.

💼 Career

Knowing how to write tests with SimpleTestCase and TestCase is a key skill for Django developers to maintain reliable applications.

1

Create a simple function to test

Create a function called add_numbers that takes two parameters a and b and returns their sum.

Django

# Your code here

Hint

Define a function with two parameters and return their sum using return a + b.

2

Create a Django model for testing

Create a Django model called Book with a single field title that is a CharField with max length 100.

Django

def add_numbers(a, b):
    return a + b

# Your code here

Hint

Import models from django.db and define a class Book inheriting from models.Model. Add a title field as models.CharField(max_length=100).

3

Write a SimpleTestCase for the add_numbers function

Write a test class called AddNumbersTests that inherits from SimpleTestCase. Add a test method test_add that asserts add_numbers(3, 4) equals 7.

Django

def add_numbers(a, b):
    return a + b

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)

# Your code here

Hint

Import SimpleTestCase from django.test. Define a test class inheriting from it. Write a test method using self.assertEqual to check the function result.

4

Write a TestCase for the Book model

Write a test class called BookModelTests that inherits from TestCase. Add a test method test_create_book that creates a Book with title 'Django Basics' and asserts the book count is 1.

Django

def add_numbers(a, b):
    return a + b

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)

from django.test import SimpleTestCase

class AddNumbersTests(SimpleTestCase):
    def test_add(self):
        self.assertEqual(add_numbers(3, 4), 7)

# Your code here

Hint

Import TestCase from django.test. Define a test class inheriting from it. Create a Book instance and assert the count is 1.

Practice

1. Which Django test class should you use when your test needs to access the database?

easy

A. StaticLiveServerTestCase

B. TestCase

C. SimpleTestCase

D. TransactionTestCase

Solution

1. Step 1: Understand the purpose of TestCase

   TestCase is designed for tests that require database access and setup.

2. Step 2: Compare with SimpleTestCase

   SimpleTestCase is used when no database interaction is needed.

3. Final Answer:

   TestCase -> Option B

4. Quick Check:

   Database tests = TestCase [OK]

Hint: Use TestCase if your test touches the database [OK]

Common Mistakes:

• Using SimpleTestCase for database tests
• Confusing TransactionTestCase with TestCase
• Assuming SimpleTestCase can access the database

2. Which of the following is the correct way to import SimpleTestCase in a Django test file?

easy

A. from django.test import SimpleTestCase

B. import SimpleTestCase from django.test

C. from django.test.simple import SimpleTestCase

D. from django.test import simpletestcase

Solution

1. Step 1: Recall Django test imports

   Django provides SimpleTestCase in the django.test module.

2. Step 2: Check syntax correctness

   Correct Python import syntax is from module import ClassName.

3. Final Answer:

   from django.test import SimpleTestCase -> Option A

4. Quick Check:

   Correct import syntax = from django.test import SimpleTestCase [OK]

Hint: Use 'from django.test import SimpleTestCase' to import [OK]

Common Mistakes:

• Using wrong import syntax
• Trying to import from non-existent submodules
• Incorrect capitalization in import statements

3. What will be the output when running this test code?

from django.test import SimpleTestCase

class MyTests(SimpleTestCase):
    def test_addition(self):
        self.assertEqual(2 + 3, 5)

    def test_database(self):
        from myapp.models import Item
        self.assertEqual(Item.objects.count(), 0)

medium

A. Both tests pass successfully

B. Both tests fail

C. test_addition passes, test_database raises an error

D. test_addition fails, test_database passes

Solution

1. Step 1: Analyze SimpleTestCase behavior

   SimpleTestCase does not set up the database, so database queries will fail.

2. Step 2: Check each test method

   test_addition is a simple math check and will pass. test_database tries to query the database, causing an error.

3. Final Answer:

   test_addition passes, test_database raises an error -> Option C

4. Quick Check:

   SimpleTestCase blocks DB access = test_addition passes, test_database raises an error [OK]

Hint: SimpleTestCase blocks DB; DB queries cause errors [OK]

Common Mistakes:

• Assuming SimpleTestCase allows database queries
• Expecting all tests to pass
• Ignoring import errors from models

4. You wrote a test class inheriting from TestCase but your tests fail with errors about database access. What is a likely cause?

medium

A. You forgot to run migrations before testing

B. You used SimpleTestCase instead of TestCase

C. You did not import TestCase correctly

D. Your test methods are missing the self parameter

Solution

1. Step 1: Understand database setup in tests

   TestCase requires the test database to be migrated before running tests.

2. Step 2: Identify common causes of DB errors

   Failing to run migrations causes database errors even if TestCase is used.

3. Final Answer:

   You forgot to run migrations before testing -> Option A

4. Quick Check:

   DB errors often mean missing migrations [OK]

Hint: Run migrations before tests using TestCase [OK]

Common Mistakes:

• Confusing SimpleTestCase with TestCase
• Ignoring migration commands
• Missing self in test method signatures

5. You want to write tests that check both simple logic and database queries in your Django app. How should you organize your test classes?

hard

A. Use TestCase for logic tests and SimpleTestCase for database tests

B. Use only SimpleTestCase for all tests

C. Use only TestCase for all tests

D. Use SimpleTestCase for logic tests and TestCase for database tests

Solution

1. Step 1: Separate tests by database need

   Logic-only tests do not need database setup, so SimpleTestCase is faster and sufficient.

2. Step 2: Use TestCase for database tests

   Tests that query or modify the database require TestCase to set up the test database.

3. Final Answer:

   Use SimpleTestCase for logic tests and TestCase for database tests -> Option D

4. Quick Check:

   Split tests by DB need: SimpleTestCase vs TestCase [OK]

Hint: Use SimpleTestCase for logic, TestCase for DB tests [OK]

Common Mistakes:

• Using TestCase for all tests unnecessarily
• Trying to run DB tests with SimpleTestCase
• Mixing test types in one class