``Whoa ...that went fast ...how about a recap?'' No problem. Here's what we did:
Write one test.
Compile the test. It should fail (because you haven't implemented anything yet).
Implement just enough to compile. (Refactor first if necessary.)
Run the test and see it fail.
Implement just enough to make the test pass.
Run the test and see it pass.
Refactor for clarity and "once and only once".
Repeat from the top.
One of the great things to come out of the recent Extreme Programming movement has been to bring unit testing to the forefront of every developers thought process.
