Question 1
When using a dedicated tests/ directory inside a Django app, how can a developer run a specific test method from command line?
python manage.py test app.tests
python manage.py test
python manage.py test app.tests.MyTestCase.test_method
python manage.py test app.tests.MyTestCase
Question 2
What base class is typically used for writing unit tests in Django?
django.test.SimpleTestCase
django.tests.UnitTest
unittest.TestSuite
django.test.TestCase
Question 3
Which of these is NOT a benefit of writing unit tests in a Django project?
Eliminating the need for code reviews
Early detection of bugs
Preventing regression when code changes
Making collaboration among developers safer
Question 4
What does organizing tests across multiple files or directories in Django allow when project grows?
Avoid running migrations
Better structure and easier maintenance of large test suites
Running only certain parts of framework
Combining test output with production logs
Question 5
What design approach describes writing tests before writing application code, then writing the minimal code to pass tests, and repeating. hich is often used in Django-REST projects?
Behavior-Driven Development
Waterfall Model
Code-First Development
Test-Driven Development (TDD)
Question 6
What is the typical flow inside a Django unit test class when testing model behaviour (e.g. create, update, delete)?
Setup → Execute → Assert → Cleanup
Define URLs → Migrate → Run tests → Print response
Import packages → Write models → Run server → Test manually
Create views → Run browser tests → Export results
There are 6 questions to complete.