Take control of your guards

By default, guard runs all your stuff on start and after the tests you are working on passes. In smaller projects, this is okay because your test suite can run a little faster. However, when you accidentally pass all tests on a big project, you’ll be doing quite a bit of waiting before you get back into your TDD cycle.

You can imagine how all that waiting can add up. Here’s how you can set up rspec and cucumber guards such that they only run all when you tell them to:

guard 'rspec', :version => 2, :all_on_start => false, :all_after_pass => false do
# ...
guard 'cucumber', :all_on_start => false, :all_after_pass => false do
  1. minatomirai reblogged this from jaryl
  2. jaryl posted this