Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Ayende Rahien commented on Legacy Driven DevelopmentThanks, fixed. http://ayende.com/3564/legacy-driven-development#comment4http://ayende.com/3564/legacy-driven-development#comment4Thu, 28 Aug 2008 04:05:43 GMTjdn commented on Legacy Driven DevelopmentThis is nice. I can relate. http://ayende.com/3564/legacy-driven-development#comment3http://ayende.com/3564/legacy-driven-development#comment3Thu, 28 Aug 2008 01:36:17 GMTJason Stangroome commented on Legacy Driven DevelopmentLast time I was doing something similar to this I implemented the diff between my output and the known good output as an automated test. http://ayende.com/3564/legacy-driven-development#comment2http://ayende.com/3564/legacy-driven-development#comment2Wed, 27 Aug 2008 22:22:14 GMTSteve Smith commented on Legacy Driven DevelopmentHi Oren, Yes, this is something Feathers talks about in his Legacy Code book, where he equates such tests to clamping down a piece of wood one is working with to ensure it doesn't move while it's being worked upon. The tests help ensure the system keeps doing what it did before, which is valuable when you start hacking at it. One quick typo, in your 2nd to last paragraph I think you meant to say "...but it *does* ensure no regression..." http://ayende.com/3564/legacy-driven-development#comment1http://ayende.com/3564/legacy-driven-development#comment1Wed, 27 Aug 2008 19:58:04 GMT