8. $ guard # starts all your “guards” in one command
$ time rspec ./spec/models/asset_spec.rb
Finished in 0.01704 seconds
real 0m3.046s
user 0m0.400s
sys 0m0.116s
9. $ guard # starts all your “guards” in one command
$ time rspec ./spec/models/asset_spec.rb
Finished in 0.01704 seconds
real 0m3.046s
user 0m0.400s
sys 0m0.116s
10. $ guard # starts all your “guards” in one command
$ time rspec ./spec/models/asset_spec.rb
Finished in 0.01704 seconds
real 0m3.046s
user 0m0.400s
sys 0m0.116s
13. Wow, looks simple...
It is, but there are some caveats when using
other gems (Devise, Mongoid, FactoryGirl)
Collection of helpful links to help you solve
(some of) them:
https://gist.github.com/1118210
How many use Rails3? How many practice TDD? How many suffer as result?\n
\n
\n
So you wait 14 seconds for Rails to boot, to run a 0.02 seconds spec. Now try to do it few times every minute.\n
So you wait 14 seconds for Rails to boot, to run a 0.02 seconds spec. Now try to do it few times every minute.\n
Spork is Tim Harper’s implementation of test server\nSpork runs on POSIX systems using fork. It also runs on windows by pre-populating a pool of ready processes (referred to here as the “magazine” strategy).\nGuard is a command line tool that easily handle events on files modifications.\n\n
Why still 3 seconds? Because there are still some things we reload on every run of specs (although this can be probably optimized).\nBesides this, you also save time by not having to run specs manually. So guard-rspec is relevant even if you don't have a big Rails project or non Rails project at all.\n\n
Why still 3 seconds? Because there are still some things we reload on every run of specs (although this can be probably optimized).\nBesides this, you also save time by not having to run specs manually. So guard-rspec is relevant even if you don't have a big Rails project or non Rails project at all.\n\n
Automatic spec runs\nGrowl notifications\nRe runs your specs until they’re green\n