That sounds like a plan. Thanks for the response. Eloy
On 24 feb 2009, at 20:41, Manfred Stienstra wrote: > > > On Feb 24, 2009, at 8:36 PM, Joshua Peek wrote: > >> >> On Tue, Feb 24, 2009 at 1:19 PM, Eloy Duran >> <eloy.de.en...@gmail.com> wrote: >>> I've also been worried about the lack of testing present in some >>> commits lately. ActionPack, and especially the Rack related code, >>> seem >>> to lack lots of necessary testing. >>> Afaik the Rails policy used to be; have good test coverage or don't >>> commit. Has this been changed? >> >> Many of those changes are related to development reloading which is >> really hard to test with traditional unit tests. This has been really >> frustrating on my part because I have to manually run though some >> stupid checklist for development reloading vs production for every >> patch I accept related to this. >> >> Seriously, if you have any good ideas how to automate real functional >> tests in this area I'd love to get them in. > > My first intuition is to spawn new Rails process from a test and see > if it behaves the way it should. I'll try to free up some time > tomorrow to give it a try. > > Manfred > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
