Django Django Testing & Debugging 3

Question 1

What does `TransactionTestCase` provide that `TestCase` does not?

Accepted Answer

Ability to test code that uses transaction.commit() or transaction.on_commit()

Answer

TransactionTestCase flushes the database instead of using rollbacks, allowing code that depends on actual commits (like on_commit hooks) to be tested correctly.

Question 2

How can you run only tests inside a specific Django app using the manage.py test command?

Accepted Answer

python manage.py test myapp

Answer

Passing the app label directly (e.g., python manage.py test myapp) scopes test discovery to that app only.

Question 3

What is the purpose of Django's `RequestFactory`?

Accepted Answer

Creating request instances to pass directly to view functions without middleware

Answer

RequestFactory produces request objects that can be passed directly to view functions, bypassing middleware and URL routing for fast, isolated view unit tests.

Question 4

Which Django logging handler is recommended to capture log output during tests for inspection?

Accepted Answer

logging.handlers.MemoryHandler or assertLogs context manager

Answer

Python's assertLogs context manager (available since Python 3.4) captures log records during a block so you can assert what was logged without real I/O.

Question 5

What is the correct way to test a Django signal receiver to verify it was called?

Accepted Answer

Use unittest.mock.patch on the receiver and assert it was called

Answer

Patching the receiver function with unittest.mock allows you to assert it was called with the expected arguments when the signal is fired.

Django Practice Test

Django Practice Test

Django Django Testing & Debugging 3