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

Tracking down a problem in Django


This book has been written using the latest available Django release at the time of writing. Early on that was Django 1.1. Then, during the course of writing, Django 1.1.1 was released and everything written after that release date used Django 1.1.1. The three 1s in that release number are the major, minor, and micro release numbers. (A missing micro number, as in Django 1.1, is an implied 0.) Django 1.1.1, since it has an explicit micro number, is called a micro release. The only changes made in micro releases are bug fixes, thus micro releases are 100 percent backwards compatible with the previous release. While a change in a major or minor version number may involve some backwards-incompatible changes that require code adjustments, the only difference you will see in updating to a new micro release is fewer bugs. Therefore, it is always recommended to run the latest micro release for the major.minor version you are using.

Despite this advice and compatibility...