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
Credits
About the Author
About the Reviewer
Preface
Index

Recording Survey responses


We've already got test data we can use to exercise processing survey responses, so we do not need to add any data to our development database for the next step. Furthermore, nothing needs to be changed in the template to support submitting responses. It already includes a submit button in the HTML form, and specifies that the form data should be submitted as an HTTP POST when the form is submitted. Right now the Submit button will work, in that it can be pressed and no error will occur, but the only result will be that the page is re-displayed. This is because the view code does not attempt to distinguish between a GET and a POST, and just treats all requests as though they were GET requests. Thus, it is the view code we need to change to add support for handling POST requests as well as GET requests.

Coding support for recording Survey responses

The view code, then, needs to change to check what method is specified in the request. The handling of a GET request should...