Comments on: Test Driven Design using mocks- Lessons Learnt (Part 2) http://isaiahperumalla.wordpress.com/2008/05/28/test-driven-design-using-mocks-lessons-learnt-part-2/ Thoughts on Object Oriented Design, Smalltalk, Behaviour Driven Development and .NET Sun, 20 Sep 2009 20:17:41 +0000 http://wordpress.com/ hourly 1 By: isaiahperumalla http://isaiahperumalla.wordpress.com/2008/05/28/test-driven-design-using-mocks-lessons-learnt-part-2/#comment-60 isaiahperumalla Tue, 03 Feb 2009 20:41:32 +0000 http://isaiahperumalla.wordpress.com/?p=9#comment-60 @Aaron Thanks, thats a good question. this example was simply to demonstrate TDD using mocks. An alternate solution would be Renderer#PrintSale(Sale), this probably makes more sense depending on the domain. I will write a post on some of the alternatives and the refactoring the interaction model. you might find this article useful <a href="http://msdn.microsoft.com/en-ca/magazine/dd882516.aspx" rel="nofollow">http://msdn.microsoft.com/en-ca/magazine/dd882516.aspx</a> @Aaron
Thanks, thats a good question. this example was simply to demonstrate TDD using mocks.
An alternate solution would be Renderer#PrintSale(Sale), this probably makes more sense depending on the domain. I will write a post on some of the alternatives and the refactoring the interaction model.

you might find this article useful http://msdn.microsoft.com/en-ca/magazine/dd882516.aspx

]]> By: Aaron VonderHaar http://isaiahperumalla.wordpress.com/2008/05/28/test-driven-design-using-mocks-lessons-learnt-part-2/#comment-59 Aaron VonderHaar Tue, 27 Jan 2009 19:02:22 +0000 http://isaiahperumalla.wordpress.com/?p=9#comment-59 That's a great article! It really shows the thought process of how TDD works, and how it can lead to better design. Although now I'm a bit curious about the process that motivated you to create a Sale#PrintReceiptOn(Renderer) method rather than creating a Renderer#PrintSale(Sale) method. Have you talked about that type of design decision in any of your other blog posts? That’s a great article! It really shows the thought process of how TDD works, and how it can lead to better design.

Although now I’m a bit curious about the process that motivated you to create a Sale#PrintReceiptOn(Renderer) method rather than creating a Renderer#PrintSale(Sale) method. Have you talked about that type of design decision in any of your other blog posts?

]]> By: Test Driven Design using mocks – Lessons learnt (Part 1) « Isaiah Perumalla http://isaiahperumalla.wordpress.com/2008/05/28/test-driven-design-using-mocks-lessons-learnt-part-2/#comment-18 Test Driven Design using mocks – Lessons learnt (Part 1) « Isaiah Perumalla Wed, 28 May 2008 22:32:48 +0000 http://isaiahperumalla.wordpress.com/?p=9#comment-18 [...] between objects an abstract level”. I will try explaining by giving an example in the next post Possibly related posts: (automatically generated)TDD [...] [...] between objects an abstract level”. I will try explaining by giving an example in the next post Possibly related posts: (automatically generated)TDD [...]

]]>