If you're just getting started with TDD or developer testing in general, you'll need to know why developer testing is a good idea and the basics of what makes good developer tests. A good starting place is this Kent Beck presentation. Kent Beck is the creator of XP, which is where TDD was originally defined.

Here are some useful links to expand your understanding of TDD. Make use of these as you learn to enact TDD. Some of these links are also good resources for on-going support and information.

• The TDD: Wikipedia entry gives an overview of TDD and links to other TDD resources.
• James Carr's TDD Anti-pattern Catalogue lists some things to avoid when adopting TDD.
• The TDD Mailing List is a discussion forum for TDD questions and issues.
• Testdriven.com is a developer testing site with a wealth of information, news, and partner links about developer testing.

Once you're familiar with the basics of TDD, select various tasks to view more detail about what needs to be done to perform the task. If you'll be creating a capability pattern or delivery process that includes TDD, see Using the TDD Practice in Context. This shows one example of how TDD can be used in conjunction with other activities and capability patterns to create a pattern for developing software. This is only one possible example - there are many was to use TDD with other development practices.