tag:blogger.com,1999:blog-8514833315479218736.post3117577714225832947..comments2023-04-02T18:48:37.334+03:00Comments on Fresh.Thoughts: Interaction vs stateful tests, or Falling for Need-Driven Developmentuluhttp://www.blogger.com/profile/09205790793910716812noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8514833315479218736.post-80800053067541869942008-06-26T12:39:00.000+04:002008-06-26T12:39:00.000+04:00As I said, it's probably personal. A little more u...As I said, it's probably personal. A little more upfront thinking and a couple of diagrams would have saved me I guess, but I'm not that kind of guy.<BR/><BR/>I've been writing functional tests first since then, and the confidence it gives me makes it much better. I might skip some refactoring, but at least I'm sure that this stuff works.uluhttps://www.blogger.com/profile/09205790793910716812noreply@blogger.comtag:blogger.com,1999:blog-8514833315479218736.post-90543648143264713472008-06-26T02:51:00.000+04:002008-06-26T02:51:00.000+04:00It's interesting that you find NDD most valuable o...It's interesting that you find NDD most valuable on the boundary cases -- exactly where the "Mock Roles, Not Objects" paper suggest you not apply NDD.<BR/><BR/>It seems that in any top-down design approach you can find yourself "trapped" in a design that's not implementable at the lower levels.Jeremy Rosshttps://www.blogger.com/profile/09333882029426679715noreply@blogger.com