Book Image

Django 1.1 Testing and Debugging

Book Image

Django 1.1 Testing and Debugging

Overview of this book

Bugs are a time consuming burden during software development. Django's built-in test framework and debugging support help lessen this burden. This book will teach you quick and efficient techniques for using Django and Python tools to eradicate bugs and ensure your Django application works correctly. This book will walk you step by step through development of a complete sample Django application. You will learn how best to test and debug models, views, URL configuration, templates, and template tags. This book will help you integrate with and make use of the rich external environment of test and debugging tools for Python and Django applications. The book starts with a basic overview of testing. It will highlight areas to look out for while testing. You will learn about different kinds of tests available, and the pros and cons of each, and also details of test extensions provided by Django that simplify the task of testing Django applications. You will see an illustration of how external tools that provide even more sophisticated testing features can be integrated into Django's framework. On the debugging front, the book illustrates how to interpret the extensive debugging information provided by Django's debug error pages, and how to utilize logging and other external tools to learn what code is doing.
Table of Contents (17 chapters)
Django 1.1 Testing and Debugging
About the Author
About the Reviewer

Unit tests for the Survey save override method

Recall in the previous chapter that we ultimately implemented four individual tests of the Survey save override function:

  • A straightforward test of the added capability, which verifies that if closes is not specified when a Survey is created, it is auto-set to a week after opens

  • A test that verifies that this auto-set operation is not performed if closes is explicitly specified during creation

  • A test that verifies that closes is only auto-set if its value is missing during initial creation, not while saving an existing instance

  • A test that verifies that the save override function does not introduce an unexpected exception in the error case where neither opens nor closes is specified during creation

To implement these as unit tests instead of doctests, create a TestCase within the suvery/ file, replacing the sample SimpleTest. Within the new TestCase class, define each individual test as a separate test method in that TestCase, like so: