After reading the first two parts of this article, you should have enough information to strike boldly and apply test-driven development to your projects. At first you're likely to find that the road is somewhat rough and bumpy, though. How do you break up this module into something testable? How can you prevent your tests from becoming a burden to maintain? What exactly should you test?

This third and last part will cover some tips that should help smooth out the learning curve and make you more productive from the start. We'll also look at some of the consequences of applying TDD to a project and what kind of things you can expect on the other side of the looking glass.

Author: Noel Llopis
Published: March 6, 2005