http://sarahtaraporewalla.com/testing/a-conversation-with-a-tdder/ Sun, 29 Aug 2010 04:31:48 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://sarahtaraporewalla.com/testing/a-conversation-with-a-tdder/#comment-77 TDD: One test at a time at Mark Needham Tue, 09 Dec 2008 12:10:28 +0000 http://sarahtaraporewalla.com/thoughts/?p=111#comment-77 [...] My colleague Sarah Taraporewalla has written a series of posts recently about her experiences with TDD and introducing it at her current client. [...] [...] My colleague Sarah Taraporewalla has written a series of posts recently about her experiences with TDD and introducing it at her current client. [...]

]]> http://sarahtaraporewalla.com/testing/a-conversation-with-a-tdder/#comment-76 Sarah Mon, 08 Dec 2008 18:30:13 +0000 http://sarahtaraporewalla.com/thoughts/?p=111#comment-76 @mats - it maybe too early, but in this conversation I wanted to demonstrate how setup could be reduced by adding builders. Every time I add a builder after I have a few tests, I always regretting not doing it from the start, especially as it is not too much work to add one. Also, yes a third test would be good, but I thought the example was getting too long for a post. Thanks for the feedback @mats – it maybe too early, but in this conversation I wanted to demonstrate how setup could be reduced by adding builders. Every time I add a builder after I have a few tests, I always regretting not doing it from the start, especially as it is not too much work to add one. Also, yes a third test would be good, but I thought the example was getting too long for a post. Thanks for the feedback

]]> http://sarahtaraporewalla.com/testing/a-conversation-with-a-tdder/#comment-75 mats Mon, 08 Dec 2008 17:39:21 +0000 http://sarahtaraporewalla.com/thoughts/?p=111#comment-75 Thanks, I enjoyed this article. Two things though: I would argue that the builder was introduced too early. Part of driving the design with tests is introducing patterns only when the code is screaming out for them -- this is debatable but I didn't see a need just yet. Second, we could make the two tests pass by always returning a list of songs with drums. I would thus write a third test with a different instrument. Thanks, I enjoyed this article. Two things though: I would argue that the builder was introduced too early. Part of driving the design with tests is introducing patterns only when the code is screaming out for them — this is debatable but I didn’t see a need just yet.
Second, we could make the two tests pass by always returning a list of songs with drums. I would thus write a third test with a different instrument.

]]>