AvocadoSoftware.com

Jeremy Miller has posted quite a response to a question asked by Jay Kimble on unit testing with the Microsoft AJAX Extentions. Filtering through most of the answer provided by Jeremy (which, by the way, none of his answers seems "odd" or "wrong" to me... all seemed like the right way to go), I found some excellent links to Jeremy's history of blog posts concerning getting started with TDD. Quoted here, is the same list.

• TDD Design Starter Kit: It’s All about Assigning Responsibilities
• TDD Design Starter Kit - State vs. Interaction Testing
• TDD Design Starter Kit - Dependency Inversion Principle
• TDD Design Starter Kit – Responsibilities, Cohesion, and Coupling
• TDD Design Starter Kit - Static Methods and Singletons May Be Harmful
• Succeed with TDD by designing with TDD
• Unit Testing Business Logic without Tripping Over the Database
• Haacked on TDD and Jeremy's First Rule of TDD
• Jeremy's Second Law of TDD: Push, Don't Pull
• Achieve Better Results by following Jeremy's Third Law of TDD: Test Small Before Testing Big - I think this is the most important lesson for making TDD work for you (ed: Jeremy's words, but I agree 100%)
• How much design before unit testing, and how much design knowledge before TDD?
• So How do You Introduce TDD into an Organization or Team?
• Mock Objects and Stubs: The Bottle Brush of TDD
• Why and When to Use Mock Objects
• Best and Worst Practices for Mock Objects
• Mock Objects are your Friend

What I find ironic about Jeremy's very large, very information, and very well written post, is that his actual post does not follow some of the rules and philosophies that he preaches about his code - there's more than one concern being addressed (TDD in AJAX vs. TDD in RAD). LOL... just had to poke fun at that for a second. I'm an avid reader of Jeremy's blog and continuously make reference to materials that he produces in my daily work.