After working on this for several hours, I finally rooted out the problem enough to turn up Eric Anderson's post from Mar 2:
> I seem to be having a dependency issue when running my test while > applying a mixin implemented by an engine into my Application > controller. I found a work around but wanted to post the problem, cause > and workarounds in hope that a solution can be put into the Engines plugin. > [...] > 4. The testing extensions require 'test_help' provided by Rails. > > 5. 'test_help' in requires 'application'. This loads my > ApplicationController class. > > 6. My ApplicationController tries to include my mixin but it cannot find > the module because my engine has not initialized yet (since it comes > after the engine plugin alphabetically). Hence leading to my problem. > > > Workarounds: > > 1. Make the "engines" plugin load after the problem plugin > 2. Comment out the "require 'test_help'". It is not necessary anyway > since the test_helper generated by rails requires it later. Just wanted to say "Thank you, Eric"!!! I eventually came up with the same solutions, but had not yet made the connection between test_help and my application controller. Now I see. D'oh! I was hoping maybe this would have been incorporated by now, but there appears to have been no new development since the release. Add my vote for getting this fixed whenever things get rolling again. I don't see any reason why lib/engines/testing.rb should need to load test_help, since anyone doing plugin testing should be loading test_help in their own test_helper.rb (or equivalent), which would run after all plugins have been loaded. Anyone see a problem with Eric's suggested fix (#2)? Cheers, -- Michael _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
