Test-Driven Development With Django

General Review

Read this book if you want to get an actual example of how TDD might work from scratch in building a front-end application (i.e., from the feature requirements, to specifying how the frontend interactions should be, and down to the actual unit test).

A way to do TDD is to use functional tests to guide the TDD. The way to do this might be to write the functional test in comments first, and implement just enough of the test to get a failing test. We can then proceed to write the first unit test.
Misconception: It is troublesome to use Selenium to make UI functional tests to drive TDD.

When doing unit test in the context of web frameworks, consider the following:
- How to partition the tests: whether it is easy / feasible to test routing separately from the controllers, to test the model logic separately from the controllers, or whether we have to test end-to-end from the URL to the response

Example of how to write functional tests for standard web application that is a thin wrapper around database
Beyond the basic CRUD, what other complexities I need to be comfortable with. E.g.:
- Using production level database
- Full QA testing (e.g., with fuzzing etc.)
- Load testing (e.g., with Locust or ab - Apache HTTP server benchmarking tool)
- Authentication
- Tagging support
- Integration with search providers like Solr
- Caching with Celery