Django Django Testing & Debugging 2

Question 1

When using `TestCase.setUpTestData()`, when is the data created relative to the test methods?

Accepted Answer

Once per test class, shared across all tests

Answer

setUpTestData() creates database objects once at the class level, improving performance by avoiding repeated setup for every test method.

Question 2

Which tool is used in Django to mock database queries and avoid hitting the real database in unit tests?

Accepted Answer

unittest.mock.patch

Answer

Python's unittest.mock.patch is the standard way to mock functions, including Django ORM calls, in unit tests.

Question 3

What does Django's `--keepdb` flag do when running tests?

Accepted Answer

Reuses the existing test database instead of recreating it

Answer

--keepdb skips the database destroy/create step between test runs, significantly speeding up subsequent test runs.

Question 4

What is the Django `DEBUG` setting typically set to in the test environment?

Accepted Answer

False, to match production behavior

Answer

Django's test runner sets DEBUG=False by default so tests run in an environment closer to production, revealing issues hidden by debug mode.

Question 5

Which Django class allows you to write tests that start a live HTTP server for browser-based testing?

Accepted Answer

django.test.LiveServerTestCase

Answer

LiveServerTestCase starts a real HTTP server in a separate thread so external tools like Selenium can make real HTTP requests during tests.

Django Practice Test