Write test cases.

[garnertb]

Each app has tests and docstrings which explains the tests.

[jillson]

1) Does it make sense to do any javascript unit tests 2) When I deploy this or another django project somewhere, the first thing I typically do (even before I sync the DB or hit the page via browser) is run python manage.py shell which gives me a decent confidence that the DB is up, we have a valid password to it, firewall stuff isn't an issue, and that all the libraries I need are installed in my virtualenv). Does it make sense to add a new manage.py management option for checkconfig (and does paver already have something like this I haven't been using?) and does this fall under test cases or a separate issue

[garnertb]

1) Yes, checkout the newer LiveServerTestCase (https://docs.djangoproject.com/en/dev/topics/testing/tools/#liveservertestcase) to include client side tests in the django test modules.

2) I would consider those smoke tests which should be included in this issue. They can be written as unit tests and run them before the rest of the tests and maybe in the pre_syncdb hook.

[jaycrossler]

We'll close this Issue as it's too broad, and start using individual test cases in the future.