TestCase and SimpleTestCase in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of Django's TestCase class?

The <code>TestCase</code> class is used to write tests that interact with the database. It sets up a test database, runs tests, and then rolls back changes to keep tests isolated.

beginner

How does SimpleTestCase differ from TestCase in Django?

SimpleTestCase is used for tests that do not require database access. It runs faster because it skips database setup and teardown.

intermediate

Why should you use TestCase instead of SimpleTestCase when testing models?

Because models interact with the database, TestCase provides a test database environment needed to safely test database operations.

intermediate

What happens to the database after each test method in a Django TestCase?

Django rolls back any changes made during the test, restoring the database to its initial state for the next test.

beginner

Can you use SimpleTestCase to test views that do not access the database?

Yes, SimpleTestCase is suitable for testing views or functions that do not require database access, making tests faster.

Which Django test class should you use to test database models?

A StaticLiveServerTestCase

B TestCase

C SimpleTestCase

D TransactionTestCase

TestCase sets up a test database and is designed for testing models.

What is a key advantage of using SimpleTestCase over TestCase?

A It runs tests faster by skipping database setup

B It can test asynchronous code only

C It automatically creates test data

D It supports database transactions

SimpleTestCase skips database setup, so tests run faster when no database is needed.

What does Django do after each test method in a TestCase?

A Saves test results to a file

B Commits all database changes

C Deletes the test database

D Rolls back database changes

Django rolls back database changes to keep tests isolated and consistent.

Which test class is best for testing a view that only returns a static HTML page?

A SimpleTestCase

B TestCase

C LiveServerTestCase

D TransactionTestCase

SimpleTestCase is ideal for tests that do not require database access, like static views.

If you want to test database transactions explicitly, which Django test class should you use?

A SimpleTestCase

B TestCase

C TransactionTestCase

D StaticLiveServerTestCase

TransactionTestCase allows testing of database transactions and does not wrap tests in atomic blocks.

Explain when and why you would use Django's TestCase versus SimpleTestCase.

Think about whether your test needs to talk to the database or not.

Describe what happens to the database state after each test method in a Django TestCase.

Imagine cleaning up after each test so the next test starts fresh.