TestCase and SimpleTestCase in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Difference in database usage between TestCase and SimpleTestCase

What happens when you run a test method inside a Django SimpleTestCase that tries to access the database?

Django

from django.test import SimpleTestCase
from myapp.models import MyModel

class MySimpleTest(SimpleTestCase):
    def test_db_access(self):
        count = MyModel.objects.count()
        self.assertEqual(count, 0)

A The test raises an error because SimpleTestCase does not set up the test database.

B The test silently ignores the database call and passes.

C The test runs successfully and counts the objects in the database.

D The test runs but always returns zero regardless of database content.

💡 Hint

Think about which test class sets up the test database.

SimpleTestCase does not set up or use the test database. Any database access inside it will raise an error.

Only TestCase sets up a test database and allows database queries.

❓ state_output

intermediate

Effect of TestCase on database state between tests

Given this Django TestCase class, what will be the count of MyModel objects in the second test method?

Django

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

class MyTest(TestCase):
    def test_create(self):
        MyModel.objects.create(name='test')
        self.assertEqual(MyModel.objects.count(), 1)

    def test_count(self):
        count = MyModel.objects.count()
        print(count)

A 2

B 0

C Raises an error because the database is not available.

D 1

💡 Hint

Remember how TestCase resets the database between tests.

Django's TestCase resets the test database after each test method, so the second test sees an empty database.

📝 Syntax

advanced

Correct way to write a Django TestCase with setup

Which option correctly defines a Django TestCase with a setup method that creates a model instance before each test?

A

class MyTest(TestCase):
    def setUp(self):
        MyModel.objects.create(name='setup')

    def test_example(self):
        self.assertEqual(MyModel.objects.count(), 1)

B

class MyTest(TestCase):
    def setup(self):
        MyModel.objects.create(name='setup')

    def test_example(self):
        self.assertEqual(MyModel.objects.count(), 1)

C

class MyTest(TestCase):
    def SetUp(self):
        MyModel.objects.create(name='setup')

    def test_example(self):
        self.assertEqual(MyModel.objects.count(), 1)

D

class MyTest(TestCase):
    def set_up(self):
        MyModel.objects.create(name='setup')

    def test_example(self):
        self.assertEqual(MyModel.objects.count(), 1)

💡 Hint

Check the exact method name Django expects for setup.

Django expects the setup method to be named exactly setUp with camel case.

Other variations like setup, SetUp, or set_up are ignored.

🔧 Debug

advanced

Why does this SimpleTestCase test fail with AttributeError?

Consider this test code. Why does it raise AttributeError: 'Client' object has no attribute 'login'?

Django

from django.test import SimpleTestCase

class MySimpleTest(SimpleTestCase):
    def test_login(self):
        logged_in = self.client.login(username='user', password='pass')
        self.assertTrue(logged_in)

A SimpleTestCase does not provide a full test client with login support.

B The test is missing a call to super().setUp() to initialize the client.

C The client attribute is missing in SimpleTestCase.

D The login method requires a database, which SimpleTestCase does not set up.

💡 Hint

Think about what login requires internally.

The login method requires database access to check user credentials.

SimpleTestCase does not set up the database, so login fails with AttributeError.

🧠 Conceptual

expert

Why choose SimpleTestCase over TestCase for some tests?

Which reason best explains why you might use SimpleTestCase instead of TestCase in Django testing?

A SimpleTestCase automatically mocks all external APIs, making tests more isolated.

B SimpleTestCase supports testing with a real database, unlike TestCase which uses a mock database.

C SimpleTestCase runs faster because it skips database setup, ideal for tests that don't need the database.

D SimpleTestCase allows testing asynchronous views, which TestCase does not support.

💡 Hint

Consider the cost of database setup in tests.

SimpleTestCase is faster because it does not set up or use the test database.

It is suitable for tests that do not require database access.

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