tag:blogger.com,1999:blog-4175311048704332408.post345222008166669985..comments2024-01-01T21:38:30.438-08:00Comments on Can't Grok, Won't Grok: TDD – Getting Started with Test-Driven DevelopmentRob Cooperhttp://www.blogger.com/profile/04578932741770127659noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4175311048704332408.post-52184101630556645552008-09-20T01:39:00.000-07:002008-09-20T01:39:00.000-07:00Thanks for the comment Sean, and please accept my ...Thanks for the comment Sean, and please accept my apologies for the delay in reply.<BR/><BR/>A very valid point, as with all of these new "things" we should always keep simplicity in our minds (reminds me of the <A HREF="http://www.43folders.com/2004/09/03/introducing-the-hipster-pda" REL="nofollow">Hipster PDA)</A> :)<BR/><BR/>However, with the automated testing, while I find it can be sometimes helpful to draft up some plans for testing, doing the traditional table with expected results and the like can be very counter-productive.<BR/><BR/>We work in an industry where the cost of "<A HREF="http://dilbert.com/strips/comic/2008-03-16/" REL="nofollow">measure twice cut once</A>" isn't a real need at the testing stage, its probably quicker to delete a line of code than scribble out/erase a line of writing.<BR/><BR/>I totally agree a "battle plan" can be real useful, but the full table is kind of overkill and merely duplicating work (IMO).Rob Cooperhttps://www.blogger.com/profile/04578932741770127659noreply@blogger.comtag:blogger.com,1999:blog-4175311048704332408.post-19902262769491543892008-09-09T04:28:00.000-07:002008-09-09T04:28:00.000-07:00Great post. I can only wonder if a good approach t...Great post. I can only wonder if a good approach to this would be to WRITE down a test plan with all of the usual data [test case, expected result, actual result]<BR/><BR/>That would make it a little easier to go about this TDD wouldn't it? Thanks for turning me onto this.<BR/><BR/>sean808080<BR/><BR/><A HREF="http://sean808080.com" REL="nofollow">sean808080.com</A>seanhttps://www.blogger.com/profile/01882279428961274610noreply@blogger.com