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

Debugging the pygooglechart results display


At this point we know the code is at the beginning of processing in the get_piechart_url method, and the current value of self indicates that the Question instance we have been called for is the question that asks What is your favorite type of TV show? That's good to know, but what we'd really like to understand is what happens as execution continues.

The step and next commands

What we'd like to do now is instruct the debugger to continue execution, but keep the debugger active. There are two commands typically used here: step (abbreviated as s) and next (abbreviated as n).

The step command begins execution of the current line and returns to the debugger at the first available opportunity. The next command also begins execution of the current line, but it does not return to the debugger until the next line in the current function is about to be executed. Thus, if the current line contains a function or method call, step is used to step into that function...