Reputation: 15409
Let's say you're working on a rails app that has a lot of initializers that call out to various external systems at startup.
When running rspec with rspec-rails it runs all the initializers, even if your test is something simple that doesn't require rails infrastructure.
I know you can use Spork to only incur this cost once but is there a way to not incur it at all? It seems silly to load up all of rails just for a simple PORO spec.
Upvotes: 7
Views: 2301
Reputation: 938
Upvotes: 3