Comments on: When to do test-driven development http://therealadam.com/archive/2009/06/29/when-to-do-test-driven-development/ Polymath practicing programming, probably procrastinating Fri, 16 Jul 2010 03:30:20 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Adam Keys http://therealadam.com/archive/2009/06/29/when-to-do-test-driven-development/comment-page-1/#comment-748 Adam Keys Tue, 30 Jun 2009 12:59:39 +0000 http://therealadam.com/?p=678#comment-748 That's an excellent point. This relies a lot on the ability to snapshot changes so you can go back if a refactoring goes wrong. That could explain why this contextual stuff is new to me, at least; few people have worked with good branching until the past few years. That’s an excellent point. This relies a lot on the ability to snapshot changes so you can go back if a refactoring goes wrong. That could explain why this contextual stuff is new to me, at least; few people have worked with good branching until the past few years.

]]> By: Iain http://therealadam.com/archive/2009/06/29/when-to-do-test-driven-development/comment-page-1/#comment-747 Iain Tue, 30 Jun 2009 12:31:02 +0000 http://therealadam.com/?p=678#comment-747 The mentions of git got me thinking; the test-first mentality is only really a big issue in centralised VCSen. With a DVCS, you can quite happily write the code, commit locally, write the tests, commit locally and then push the tests+code as a coherent chunk. In svn, doing this would be a risky proposition as someone else could easily checkout the version without tests and then write your name on the Whiteboard of Shame... The mentions of git got me thinking; the test-first mentality is only really a big issue in centralised VCSen.

With a DVCS, you can quite happily write the code, commit locally, write the tests, commit locally and then push the tests+code as a coherent chunk.

In svn, doing this would be a risky proposition as someone else could easily checkout the version without tests and then write your name on the Whiteboard of Shame…

]]>