> > I tend to approach the whole legacy thing (any code w/ no tests) from > the view espoused by Michael Feathers in his book Working Effectively > with Legacy Code: when you want to add a feature or change behaviour, > you discover where you want to make the change, analyze the parts of > the code it will impact, and add characterization tests for those > areas only. This way you're always working on stuff that has immediate > value and , little by little, you move towards a very well covered > system. > > As you suggest, no client wants to pay for testing stuff that they see > as already working - but certainly they don't you want you to break > that stuff either. > > Cheers, > David
+1 => This is exactly how I've been approaching it with a 10,000 line rails app with virtually no tests. Scott _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
