> Argh, this isn't the only problem. Try checking for namespace > intrusions in the other tests. Things like "Module Fun" sneak in and > modify other things. This whole testing suite needs some serious > refactoring. I don't think rake's tests were ever meant to have > anything outside of the test class in the same file. > > Looking at the way things are arranged, there's a lot of incompatible > duplication. Also, I noticed there's a controller_fixtures directory > that is not even being used. Wouldn't this be the prime place to put > examples of controllers that would be used in the tests, instead of > defining those controllers in the tests themselves?
What are the practical implications of these issues that you're describing? I guess I'm just not following you? The tests could certainly be broken up to have all the controllers defined in seperate files. However they're still going be run in one interpreter. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
