Comments on: Don’t refactor without unit tests http://blog.agilephp.com/2009/09/03/dont-refactor-without-unit-tests/ Dagfinn Reiersøl on PHP, agile development, Ruby and other addictive substances Fri, 23 Jul 2010 20:17:39 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Albo http://blog.agilephp.com/2009/09/03/dont-refactor-without-unit-tests/comment-page-1/#comment-657 Albo Mon, 07 Sep 2009 15:18:44 +0000 http://blog.agilephp.com/?p=1596#comment-657 I totally agree. The Legacy Code Dilemma paralyze me the first time. But once you start to write at least one Unit Test (just before you refactor a little bit of code), you're able to start with the add unit test-refactoring cycle. I totally agree. The Legacy Code Dilemma paralyze me the first time. But once you start to write at least one Unit Test (just before you refactor a little bit of code), you’re able to start with the add unit test-refactoring cycle.

]]> By: Brandon Savage http://blog.agilephp.com/2009/09/03/dont-refactor-without-unit-tests/comment-page-1/#comment-652 Brandon Savage Fri, 04 Sep 2009 18:46:48 +0000 http://blog.agilephp.com/?p=1596#comment-652 Thanks for your words about the series. I'm glad you're enjoying it. I think you're right about testing, and it reflects a test-first approach. Most applications are considerably larger than the one we're working on, and I totally believe that the unit tests should be written first. I'll make sure and link to your post in the testing entry, which will be forthcoming one week from Monday. Thanks for your words about the series. I’m glad you’re enjoying it.

I think you’re right about testing, and it reflects a test-first approach. Most applications are considerably larger than the one we’re working on, and I totally believe that the unit tests should be written first.

I’ll make sure and link to your post in the testing entry, which will be forthcoming one week from Monday.

]]>