1. Chapter 1 Beginning Testing

   1. Installing Test Modules

   2. Running Tests

   3. Interpreting Test Results

   4. Writing Your First Test

   5. Loading Modules

   6. Improving Test Comparisons

2. Chapter 2 Writing Tests

   1. Skipping Tests

   2. Skipping All Tests

   3. Marking Tests as TODO

   4. Simple Data Structure Equality

   5. Data Composition

   6. Testing Warnings

   7. Testing Exceptions

3. Chapter 3 Managing Tests

   1. Organizing Tests

   2. Checking Your Coverage

   3. Writing a Testing Library

   4. Testing a Testing Library

   5. Writing a Testing Harness

   6. Testing Across the Network

   7. Automating Test Runs

4. Chapter 4 Distributing Your Tests (and Code)

   1. Testing POD Files

   2. Testing Documentation Coverage

   3. Distribution Signatures

   4. Testing Entire Distributions

   5. Letting the User Decide

   6. Letting the User Decide (Continued)

   7. Bundling Tests with Modules

   8. Collecting Test Results

   9. Validating Kwalitee

5. Chapter 5 Testing Untestable Code

   1. Overriding Built-ins

   2. Mocking Modules

   3. Mocking Objects

   4. Partially Mocking Objects

   5. Overriding Live Code

   6. Overriding Operators Everywhere

6. Chapter 6 Testing Databases

   1. Shipping Test Databases

   2. Testing Database Data

   3. Using Temporary Databases

   4. Mocking Databases

7. Chapter 7 Testing Web Sites

   1. Testing Your Backend

   2. Testing Your Frontend

   3. Record and Play Back Browsing Sessions

   4. Testing the Validity of HTML

   5. Running Your Own Apache Server

   6. Testing with Apache-Test

   7. Distributing Modules with Apache-Test

8. Chapter 8 Unit Testing with Test::Class

   1. Writing Test Cases

   2. Creating Test Fixtures

   3. Inheriting Tests

   4. Skipping Tests with Test::Class

   5. Marking Tests as TODO with Test::Class

9. Chapter 9 Testing Everything Else

   1. Writing Testable Programs

   2. Testing Programs

   3. Testing Interactive Programs

   4. Testing Shared Libraries

1. Colophon

The Developer's Notebook series is modeled on the tradition of laboratory notebooks. Laboratory notebooks are an invaluable tool for researchers and their successors. The purpose of a laboratory notebook is to facilitate the recording of data and conclusions as the work is being conducted, creating a faithful and immediate history. The notebook begins with a title page that includes the owner's name and the subject of research. The pages of the notebook should be numbered and prefaced with a table of contents. Entries must be clear, easy to read, and accurately dated; they should use simple, direct language to indicate the name of the experiment and the steps taken. Calculations are written out carefully and relevant thoughts and ideas recorded. Each experiment is introduced and summarized as it is added to the notebook. The goal is to produce comprehensive, clearly organized notes that can be used as a reference. Careful documentation creates a valuable record and provides a practical guide for future developers.