Running test automatically is great in theory, but the go-to solution when using RSpec based on Spork and Guard is mediocre to say the least. It forces you to remember all details of which component does what, who trigges what, what's reloaded at what stage and so on. Despite the fact that this was really confusing to start off with, maybe you're like me and never really cared to learn these details (and you really shouldn't need to!).
This is the setup I found working for me for plain Rails 3.1+ and RSpec.
- Elaborate explanation on StackOverflow
- Description of
Spork.trap
, including derivation you'll need to make when using additional Gems like FactoryGirl - Useful options for guard-rspec