If the time taken to run the test suite is so critical, then how is the "winning" result of 7m55s any better?
In my experience any multi-minute operation invites a context switch or coffee break, and end up being roughly equivalent in practice.
In my experience any multi-minute operation invites a context switch or coffee break, and end up being roughly equivalent in practice.
We use a tool called `rake autospec` at Discourse which is a smart test runner. I personally like the vim integration we built.
The way it works...
1. Run `bin/rake autospec` in a terminal 2. I head to the code I want to change, I change the code 3. The spec runner figures out what the right test is run and runs that. 4. While it is busy running specs at any time it can be interrupted by saving a "*.spec" file in which case the spec runner will run the spec at the cursor
This has worked wonderfully well for us.
1. just
2. like
3. this