Andrew Timberlake wrote: > I don't think that this is a good idea at all. > Definitely start testing immediately but I wouldn't rewrite the app at all.
It ain't a rewrite. Imagine if you could put a bookmark at one end of all your source. Above the bookmark is completely tested and below the bookmark is incidentally tested or not at all. If you open a new project folder and start TDDing each feature, passing each test by copying code in, then what you are really doing is simply moving that bookmark down thru all your source until it hits the end. If opening a new folder squicks you out, then comment out _all_ the code, and TDD it to uncomment it. Either way, the resulting velocity is much higher than raw development. > For every bug fix and change, make sure you write tests for the > functionality you are working on (in a TDD/BDD way - before changing > the code.) That is the advice from /Working Effectively with Legacy Code/ by Mike Feathers. -- Phlip http://flea.sourceforge.net/resume.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
