Comments on: TDD: Mock expectations in Setup http://www.markhneedham.com/blog/2008/12/19/tdd-mock-expectations-in-setup/ Thoughts on Software Development Sat, 11 Feb 2012 23:17:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Coding: Paying attention at Mark Needham http://www.markhneedham.com/blog/2008/12/19/tdd-mock-expectations-in-setup/comment-page-1/#comment-36411 Coding: Paying attention at Mark Needham Sun, 09 May 2010 13:11:20 +0000 http://www.markhneedham.com/blog/?p=755#comment-36411 [...] Another somewhat related situation where I've noticed a similar problem is when we have several tests which require a certain method to be stubbed out and in the interests of reducing duplication we pull that up into a setup method. [...] [...] Another somewhat related situation where I've noticed a similar problem is when we have several tests which require a certain method to be stubbed out and in the interests of reducing duplication we pull that up into a setup method. [...]

]]> By: TDD: Asserting on test dependency code at Mark Needham http://www.markhneedham.com/blog/2008/12/19/tdd-mock-expectations-in-setup/comment-page-1/#comment-21557 TDD: Asserting on test dependency code at Mark Needham Wed, 19 Aug 2009 13:23:28 +0000 http://www.markhneedham.com/blog/?p=755#comment-21557 [...] Ensure that all the setup for the test is done inside the test and not in setup methods. [...] [...] Ensure that all the setup for the test is done inside the test and not in setup methods. [...]

]]> By: mike http://www.markhneedham.com/blog/2008/12/19/tdd-mock-expectations-in-setup/comment-page-1/#comment-2144 mike Fri, 19 Dec 2008 18:25:59 +0000 http://www.markhneedham.com/blog/?p=755#comment-2144 In general I don't need it. I use a mock framework that allows to verify the interaction after exercising the SUT. In those cases there's no Expect to use on the setup. The only case left is when we Stub something. In those cases it is unlikely to get lucky and be able to DRY it into the setup. Usually when I Stub something it implies different values for different tests so I don't get to refactor it into the Setup. So, yes I follow DRY all the time. In this case ExpectServiceToReturnSomeValue is a Stub ... I'm calling it nowadays GivenServiceWillReturnSomeValue() ... and i'd move it into the setup if its necessary for Every test methods. In general I don’t need it. I use a mock framework that allows to verify the interaction after exercising the SUT. In those cases there’s no Expect to use on the setup.

The only case left is when we Stub something. In those cases it is unlikely to get lucky and be able to DRY it into the setup. Usually when I Stub something it implies different values for different tests so I don’t get to refactor it into the Setup.

So, yes I follow DRY all the time.

In this case ExpectServiceToReturnSomeValue is a Stub … I’m calling it nowadays
GivenServiceWillReturnSomeValue() … and i’d move it into the setup if its necessary for Every test methods.

]]>