[rspec-users] Rails code reloading in RSpec test environment?
jason.nah at gmail.com
Wed Nov 23 17:50:58 EST 2011
What's wrong with using spork? Works well for me.
The issue I've found is rails loading everything. So the only 'simple
fix' is the spork kind (ie process fork)
On 23/11/2011, at 7:46 AM, Ash Moran <ash.moran at patchspace.co.uk> wrote:
> I've worked on a couple of Rails 3 apps recently and the test feedback loop is killing me. With no modifications, it takes 15-25 seconds to run a single example. I've avoided Spork so far, but I've tried Spin. Spin shaves a few seconds off but it's still agonising. I've also experimented with multiple Guard groups and other hacks to run isolated code in lib/, but a lot of the code can't be isolated (all the controllers, for example).
> My last resort is to try and run Rails against an environment with `config.cache_classes = false`. Has anyone tried this (and got it working)? I imagine it would have to run tests over DRb, which I've only used with Spork before. The last mention of "cache_classes" on this list was in 2009, so I thought I'd check before I invested time in it in case there any major obstacles.
> Any help appreciated
>  http://jstorimer.github.com/spin/
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users