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

Before every individual test method

Answer

Once per test module

Answer

After every individual 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

django.test.mock

Answer

django.db.test.Mock

Answer

pytest.monkeypatch only

Question 3

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

Accepted Answer

Reuses the existing test database instead of recreating it

Answer

Keeps test data after each test runs

Answer

Prevents rollback after each test

Answer

Saves the test database to a file

Question 4

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

Accepted Answer

False, to match production behavior

Answer

True, so error details are visible

Answer

None, to disable error pages

Answer

Depends on the DJANGO_ENV variable

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

django.test.TestCase

Answer

django.test.SimpleTestCase

Answer

django.test.TransactionTestCase

Question 6

In Django's test client, how do you simulate a logged-in user without going through the login flow?

Accepted Answer

self.client.force_login(user)

Answer

self.client.login(user=user)

Answer

self.client.set_user(user)

Answer

self.client.authenticate(user)

Question 7

What is the Django `django-debug-toolbar` primarily used for?

Accepted Answer

Profiling SQL queries and request/response details during development

Answer

Running automated tests

Answer

Monitoring production server health

Answer

Linting Django code for errors