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

Summary


We've now come to the end of discussion of what to do when none of the other debugging techniques covered previously have succeeded in solving some problem. In this chapter, we:

  • Encountered a bug that existed in Django 1.1 and caused some of the survey application code to not behave as desired

  • Walked through the verification process of tracking down the problem to Django instead of the survey code

  • Saw how searching in the Django code tracker revealed the problem was a bug that had been fixed in Django 1.1.1, which provided an easy solution to the problem

  • Discussed options for how to proceed when problems are tracked down to bugs with fixes that are either not yet available or not available in official releases

  • Described the various community resources that exist for asking questions about behavior that seems puzzling, but doesn't seem to have been reported as a bug

  • Discussed tips for writing questions so that they get the desired helpful responses

  • Described the process of opening a new...