Ralph Shnelvar wrote: >>> Well ... I upgraded. Jeez, that was hard. Devise changed several of >>> its interfaces and it was a joy and a half tracking all(?) of them down. >> >> If you have comprehensive tests, then the tests tell you where things >> changed. >> >> If you don't have comprehensive tests, write some *now*, before you >> write any more application code. Then get in the habit of doing all new > > How would tests catch the fact that some Devise helper methods moved to > a new file any better than actually running the code?
The tests exercise the code for you. You can just run your whole test suite and get a report on what broke where, rather than having to track down all your method calls by hand. If you're using autotest, this is done for you every time a file changes. Developing without tests is fragile and negligent IMHO. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. -- 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-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
