tag:blogger.com,1999:blog-1664217632350055880.post8576876761767361973..comments2010-01-24T07:18:05.082-07:00Michael Murrayhttps://profiles.google.com/109073345657761090655noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1664217632350055880.post-90380248171034607052009-12-25T05:20:13.680-07:002009-12-25T05:20:13.680-07:00Hi Mike,<br /><br />In terms of the stubbing vs. asserting a method was called, the team I&#39;m on has found we rarely AssertWasCalled any more. Doing so explicitly couples our tests/specs to the implementation, whereas just stubbing calls in a SetUp seems easier to change without altering the fundamental assertions in our tests. <br /><br />The only time we use AssertWasCalled is for void methods to a service or similar where there is no observable side-effect from a unit perspective.<br /><br />YMMV. :)<br /><br />Regards,<br />DavidDavidhttp://www.blogger.com/profile/05155410712205848106noreply@blogger.comtag:blogger.com,1999:blog-1664217632350055880.post-82715225247285077702009-12-19T04:13:31.301-07:002009-12-19T04:13:31.301-07:00Hi Mike,<br /><br />great you continued this series.<br /><br />I think I messed things up and wrote incorrect things. In the meantime I managed to do this kata again and now I agree with you. Just forget my advice to mock it - this was wrong.<br /><br />However, I and my coworkers question if it&#39;s worth to write 30 lines of code to test a 2-lines-method? I think for this kata it will be enough to do some acceptance tests here.Tobias Walterhttp://www.blogger.com/profile/00608224689808794198noreply@blogger.com