Refactor your tests under a green bar.
I hate refactoring under a red bar. I like green. It’s pavlovian.
This lets you duplicate your existing test, break some code in the code under test, and refactor away. This will generate a pending spec if and only if both blocks fail in exactly the same way. Make a typo in your refactoring, but don’t notice because the bar is still red? Not a problem.
-
Currently only does rSpec
-
Currently not very useful as it can’t span scopes
Shunt.go do |shunt| shunt.control { true.should be_false } # original test code shunt.variable { true.should be_false } # refactor this into something nicer end
-
rSpec
-
Gem coming later
(The MIT License)
Copyright © 2009 Otto Hammersmith
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.