Why testing Django apps matters - See It in Action

Why testing Django apps matters

📖 Scenario: You are building a simple Django app that manages a list of books. You want to make sure your app works correctly every time you add new features or fix bugs.

🎯 Goal: Learn why testing Django apps is important by creating a simple test that checks if your book list view returns the correct status code.

📋 What You'll Learn

Create a Django test case class

Write a test method to check the book list view

Use Django's test client to make a GET request

Assert the response status code is 200

💡 Why This Matters

🌍 Real World

In real projects, testing ensures your website works well for users and prevents errors when updating code.

💼 Career

Knowing how to write and run tests is a key skill for Django developers to maintain reliable and professional applications.

1

Set up a Django test case class

Create a Django test case class called BookTests that inherits from django.test.TestCase.

Django

from django.test import TestCase

# Create the BookTests class here
# Your code here

Hint

Use class BookTests(TestCase): to start your test case class.

2

Add a test method for the book list view

Inside the BookTests class, add a test method called test_book_list_view_status_code that will test the book list page.

Django

from django.test import TestCase

class BookTests(TestCase):
    # Add the test method here
    # Your code here

Hint

Define a method inside the class with the name test_book_list_view_status_code.

3

Use Django test client to request the book list page

Inside the test_book_list_view_status_code method, use self.client.get("/books/") to make a GET request to the book list URL and store the response in a variable called response.

Django

from django.test import TestCase

class BookTests(TestCase):
    def test_book_list_view_status_code(self):
        # Make a GET request to '/books/' and save the response
        # Your code here

Hint

Use response = self.client.get("/books/") to get the page.

4

Assert the response status code is 200

Add an assertion inside test_book_list_view_status_code to check that response.status_code equals 200 using self.assertEqual.

Django

from django.test import TestCase

class BookTests(TestCase):
    def test_book_list_view_status_code(self):
        response = self.client.get("/books/")
        # Assert status code is 200
        # Your code here

Hint

Use self.assertEqual(response.status_code, 200) to check the page loaded successfully.

Practice

1. Why is it important to write tests for your Django app?

easy

A. To reduce the size of the app

B. To make the app run faster

C. To add more features automatically

D. To make sure the app works correctly and avoid bugs

Solution

1. Step 1: Understand the purpose of testing

   Testing helps check if the app behaves as expected and finds bugs early.

2. Step 2: Identify the main benefit of testing

   Tests ensure the app works correctly and prevents future errors.

3. Final Answer:

   To make sure the app works correctly and avoid bugs -> Option D

4. Quick Check:

   Testing = Avoid bugs [OK]

Hint: Testing finds bugs early to keep app reliable [OK]

Common Mistakes:

• Thinking tests make the app faster
• Believing tests add features automatically
• Confusing testing with app size reduction

2. Which of the following is the correct way to run tests in a Django project?

easy

A. python manage.py runserver

B. python manage.py migrate

C. python manage.py test

D. python manage.py collectstatic

Solution

1. Step 1: Recall Django commands

   Common Django commands include runserver, migrate, collectstatic, and test.

2. Step 2: Identify the command to run tests

   The command python manage.py test runs all tests in the project.

3. Final Answer:

   python manage.py test -> Option C

4. Quick Check:

   Run tests = python manage.py test [OK]

Hint: Use 'python manage.py test' to run Django tests [OK]

Common Mistakes:

• Using runserver to run tests
• Confusing migrate with testing
• Trying collectstatic for tests

3. Consider this Django test case snippet:

from django.test import TestCase

class SimpleTest(TestCase):
    def test_addition(self):
        self.assertEqual(2 + 2, 4)

What will happen when you run this test?

medium

A. The test will pass because 2 + 2 equals 4

B. The test will fail because 2 + 2 is not 4

C. The test will raise a syntax error

D. The test will be skipped automatically

Solution

1. Step 1: Understand the test logic

   The test checks if 2 + 2 equals 4 using assertEqual.

2. Step 2: Evaluate the assertion

   Since 2 + 2 is indeed 4, the assertion passes and the test succeeds.

3. Final Answer:

   The test will pass because 2 + 2 equals 4 -> Option A

4. Quick Check:

   2 + 2 = 4 test passes [OK]

Hint: assertEqual checks if values match exactly [OK]

Common Mistakes:

• Thinking 2 + 2 is not 4
• Expecting syntax errors in simple tests
• Assuming tests skip without decorator

4. You wrote this Django test but it fails with an error:

from django.test import TestCase

class MyTest(TestCase):
    def test_example(self):
    self.assertTrue(True)

What is the problem?

medium

A. Indentation error in the test method

B. Missing import for assertTrue

C. TestCase class is not imported

D. assertTrue is not a valid method

Solution

1. Step 1: Check the test method indentation

   The line self.assertTrue(True) is not indented inside the method properly.

2. Step 2: Understand Python indentation rules

   Python requires code inside functions to be indented; missing indentation causes an error.

3. Final Answer:

   Indentation error in the test method -> Option A

4. Quick Check:

   Indent code inside methods [OK]

Hint: Indent test code inside methods correctly [OK]

Common Mistakes:

• Forgetting to indent inside functions
• Assuming assertTrue needs import
• Thinking TestCase import is missing

5. You want to ensure your Django app stays bug-free as you add features. Which testing practice helps most with this?

hard

A. Write one big test covering all features at once

B. Write many small tests for each feature and run them often

C. Only test the app once before release

D. Avoid writing tests to save time

Solution

1. Step 1: Understand testing frequency and size

   Small tests for each feature catch bugs early and are easier to maintain.

2. Step 2: Recognize the benefit of running tests often

   Running tests regularly during development helps find problems quickly.

3. Final Answer:

   Write many small tests for each feature and run them often -> Option B

4. Quick Check:

   Small frequent tests = fewer bugs [OK]

Hint: Small tests + frequent runs keep app stable [OK]

Common Mistakes:

• Testing only once before release
• Writing one big test for everything
• Skipping tests to save time