I agree with doing fast, isolated test and follow the single
responsibility principle, however my problem with rake & rails is not
the execution time of tests, but the start up of rake instead.
I'm trying to use Test Driven Design, so I run test a lot and it's a
pain if every time I lost 6+ seconds for ONLY rake test start up;
inadmissible.
I think culprit is not rake itself, but start up of rails' environment.
Now, I've found the spork-testunit gem, not user-friendly as "rake
test", but a lot more faster and test execute in a blink of eyes: 0.5
sec VS 7 sec.
For me, that's the solution.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment