What to read after Test-Driven Development in Microsoft .NET?

With the clarity and precision intrinsic to the Test-Driven Development (TDD) process itself, experts James Newkirk and Alexei Vorontsov demonstrate how to implement TDD principles and practices to drive lean, efficient coding—and better design. The best way to understand TDD is to see it in action, and Newkirk and Vorontsov walk step by step through TDD and refactoring in an n-tier, .NET-connected solution. And, as members of the development team for NUnit, a leading unit-testing framework for Microsoft .NET, the authors can offer matchless insights on testing in this environment—ultimately making their expertise your own.

Test first—and drive ambiguity out of the development process:

• Document your code with tests, rather than paper
• Use test lists to generate explicit requirements and completion criteria
• Refactor—and improve the design of existing code
• Alternate programmer tests with customer tests
• Change how you build UI code—a thin layer on top of rigorously tested code
• Use tests to make small, incremental changes—and minimize the debugging process
• Deliver software that’s verifiable, reliable, and robust