On 15/12/10 2:13 PM, Dmytrii Nagirniak wrote:
On 15 December 2010 09:57, Xavier Shay <[email protected]
<mailto:[email protected]>> wrote:
On 15/12/10 9:52 AM, dnagir wrote:
Hi Guys,
I am a bit tired of waiting for for the [rails 3] specs to run
after I
save a file. After saving, I have to wait 10 secs or so for my specs
only to be executed (by autotest).
Same problem, no great solution. #1 thing I hate about rails atm.
I use this to speed up rake spec, which is a bit of a hack:
http://rhnh.net/2010/09/07/speeding-up-rails-rake
Nice hack. I wish we could do similar for Rails app. But I guess we
still need the environment in specs though.
You still get the environment, the problem with rake spec is it loads
the environment at least twice - once initially for the rake tasks, once
for spec:units, then once more for every other spec task you have (such
as spec:acceptance).
I thought the idea of Rails 3 'load lazily everything' was supposed NOT
to load everything until needed. But there's probably just too much
staff that IS needed at the beginning anyway.
Correct, especially once you start getting a number of gems hanging around
--
You received this message because you are subscribed to the Google
Groups "Ruby or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google Groups "Ruby or
Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.
