8

I have some Rspec tests that are sometimes failing with an error: Circular dependency detected while autoloading constant. These tests are multithreaded (rufus-scheduler tests), which is apparently a known problem for autoloading code (http://route.github.io/2013/11/13/rails-autoloading.html).

I can get the tests to work consistently if I set config.eager_load = true in config/environments/test.rb. However, I'm worried that this will really slow down the rest of my test suite when it grows larger. Is there any way to set this eager load option ONLY for my multithreaded tests?

Rails 4.1.4

Sterling Paramore
  • 403
  • 7
  • 15
  • 4
    Ok, so adding ````before { MyApp::Application.eager_load! }```` in my spec *seems* to be working as I wanted. Anyone know if there could be side effects or other issues I might have be worried about? – Sterling Paramore Sep 11 '14 at 20:55
  • I have the same problem in Rails 4.5. Your workaround seems to have worked for me though I don't put it in the `before` block. I just have it directly under `RSpec.describe...`. The only side effect I can think about is that you can't really set `eager_load = false` again. Any group of tests that includes this one will load the whole application. I'm hoping there's a way to eager load only specific modules/directories to reduce the impact. – jeteon May 24 '16 at 20:58
  • @SterlingParamore this question (and pondering your answer) really helped me think through rails eager loading. So, I've written it up as an answer for future reference. – Tim Diggins Jan 22 '18 at 09:23

1 Answers1

2

Add before { MyApp::Application.eager_load! } as the setup for this file/suite only. (Agreeing with @SterlingParamore above)

FYI: You need to put it in a before{} rather than just loose in the body of the describe, because otherwise it will occur whenever the file is loaded (e.g. even if you are loading that file, but targeting another spec with a tag, e.g. rspec spec --tag=focus).

Setting config.eager_load = true in your test.rb config will slow down time to first test, unless you are using Spring (which after all is designed to speed up time to first test on subsequent test runs). However, if you are using Spring, might be worth cross-referencing https://github.com/rails/spring/issues/519, though this relates to quite a different eager-loading problem.*

Tim Diggins
  • 4,364
  • 3
  • 30
  • 49