Extreme Programming Installed

Advanced Practice:Tests as Database

Here's a tip from Chet on keeping track of defects by using process elements you already have: your tests. Stop relying on a trail of paper or e-mails, or even a database, to keep track of defects. Instead, write tests to show defects. You will need to decide how you will implement a test-driven defect list. Since the unit tests must be kept at 100 percent, you must decide how to have tests that document current bugs. There are four ways to do this:

1. Define defect tests as acceptance tests (which may be below 100 percent).

2. Keep the defect tests in a separate unit test category and shift them into the production unit suite as they are worked on.

3. Defer writing the test until you are ready to begin working on the isn't ...