Ok, I spent some time digging through commits and writing tests. The tests I wrote actually don't have anything to do with reloading because I couldn't find a recent commit that required any forking or spawning to test.
http://github.com/Manfred/rails/commits/railties-tests Josh, can you point me to a specific piece of code that would require such a test? Manfred On Feb 25, 8:15 am, Manfred Stienstra <manf...@gmail.com> wrote: > >>> That sounds like a job for forking. > > >> That makes accumulating the failures from the child process > >> essentially impossible though, you'd end up with crazy output > >> intertwined with the parent process. > > Well, let's just talk code shall we (: I'll write up some stuff and > present it to the mailinglist, we can debate whether it's a good > solution afterwards. About support for testing on Windows: any help is > appreciated, I don't understand Windows. > > 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 -~----------~----~----~----~------~----~------~--~---
