Summary
We have now come to the end of discussing Django's unit test extensions to support testing web applications. In this chapter, we:
Learned how to organize unit tests into separate files instead of placing everything into a single tests.py file
Began to develop views for the survey application, and learned how to use Django's unit test extensions to test these views
Saw how to customize the admin interface by providing custom validation for one of our models, and learned how to test that admin customization
Briefly discussed some unit test extensions provided by Django that we did not encounter in any of our example tests
Learned when it might be necessary to use
TransactionTestCase
instead ofTestCase
for a test
While we have covered a lot of ground in learning how to test a Django application, there are many aspects to testing a web application that we have not even touched on yet. Some of these are more appropriately tested using tools other than Django itself. The next chapter will...