Ruby on Rails

On Fri, Dec 2, 2011 at 8:50 AM, Michael Pavling <pavling@gmail.com> wrote:

> ... and the starting place for that might be to spend some time
> getting good test coverage in place.

s/ might be / is definitely /

As someone who's taken over existing apps with little or no test
coverage (and would prefer not to repeat the experience!), I can
assure you that filling in that gap before you touch *anything* will
make your life more pleasant :-)

And if there aren't many tests, there's a good chance you'll find
code that would benefit from refactoring anyway, which will make
it easier to separate out or upgrade, whichever you choose.

FWIW,
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
http://about.me/hassanschroeder
twitter: @hassan

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.