[rspec-users] Rails code reloading in RSpec test environment?
apremdas at gmail.com
Wed Nov 23 02:19:55 EST 2011
On 23 November 2011 00:57, Justin Ko <jko170 at gmail.com> wrote:
> On Nov 22, 2011, at 4:52 PM, Andrew Premdas wrote:
>> On 22 November 2011 20:31, 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
>> Use Ruby 1.8.7 its much faster. There is a very good screencast on
>> Destroy All Software that might help also - the one about extracting
>> domain objects (or something like that).
> Anytime someone suggests using 1.8, a Chinchilla explodes. 1.9.3 has the "slow require" fix - please use that if it is your concern.
Yeh I know, but have you actually tried it out and got benchmarks to
prove that 1.9.3 is fast enough? I've been trying for the last few
weeks to get the rails test cycle going as quickly as possible. I'd
like to be using 1.9.x but its just been to slow. I've tried
fast_require patches, done lots of googling, used rvm to try different
versions etc. etc.. Currently the Rails test cycle is much faster in
1.8.7 - and for me the speed of the test cycle is the most important
thing. Using rvm I can always run the app on 1.9.x in CI and
production (so long as I create it using 1.8.x). Even using 1.8.7 the
time to run a model spec is a couple of seconds, which really is still
to slow, but its bearable. As soon as this becomes 4 or 5 seconds then
my style of programming has to change, and I don't want that.
If you have some uber fast version of 1.9.3 working reliably with
Rails 3.1.x and RVM running a single spec on an empty rails project in
less than 2 seconds - please point me in that direction with a link to
the particular patch/article/whatever.
>>>  http://jstorimer.github.com/spin/
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>> Andrew Premdas
>> rspec-users mailing list
>> rspec-users at rubyforge.org
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users