Agile development practices and good Object Oriented Design principles are supposed to enable unending, gentle modification of an existing codebase. Is this really true, though? In the course of 5+ years developing and evolving an open source framework, I’ve learned a lot of painful lessons about the issues that retard code extensions and modifications. I’ve also learned a little bit about the design decisions that dramatically increased my ability to extend the code. In this talk I’ll show several instances of how failing to heed design fundamentals introduced code …

The video is intended to be an introduction to TDD, and how actually to go about writing tests and code using TDD with Visual Studio. I hear a lot of people using the term “TDD” without really understanding it. They typically are referring to “unit testing” or sometimes even test-first development, neither of which are really TDD.
Download this QuickTime from TestDrivenDeveloper.com

In this fifth and final episode, Stephen Walther and Charlie Poole successfully view blog entries in a page and all of their tests are green. This episode ends with Charlie Poole’s thoughts on the process that they followed and ASP.NET MVC.
http://www.asp.net/learn/mvc-videos/video-409.aspx

In this fourth episode, Stephen Walther and Charlie Poole build classes that represent their blog and blog entries. Charlie Poole also demonstrates some useful NUnit tricks.
http://www.asp.net/learn/mvc-videos/video-408.aspx

In this third episode, Stephen Walther and Charlie Poole build tests that verify that their blog can return blog entries. They build unit tests for the case when there are no entries returned and the case when a single entry is returned.
http://www.asp.net/learn/mvc-videos/video-407.aspx