1) If your running 'rake spec', then don't, unless you need to do 'rake db:test:prepare' also. The 'rake spec' command combines the database rake with 'rspec spec', that's why it takes a few seconds before the tests are run. Use 'rspec spec' instead.
2) Use Spork and Autotest. Follow http://railstutorial.org/chapters/static-pages#sec:testing_tools to get Autotest setup. Note that you don't need the Spork hack with the newest version of Spork. 3) When using Autotest, consider removing 'bundle exec' from the RSpec command. In future versions of RSpec, you'll be able to do this with a configuration setting, or you can get the current RSpec master which has committed the option already (see commit here https://github.com/rspec/rspec-core/commit/1ff93b0969a0f1a6c8d4cf39ed9b7466c7eb10c8). If you want to freedom patch to get rid of 'bundle exec' see this post: http://www.arailsdemo.com/posts/36. (There's some other information in the Post #35...) I haven't seen how these tips affect Cucumber yet, so you'll have to experiment on your own for now. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
