Fix `expect { ... }.to` to work w/o rspec core #37

wants to merge 0 commits into


None yet
2 participants

myronmarston commented Oct 22, 2010

Here's the fix for the TODO David added recently. I used the test unit cuke to test using expect {...}.to w/o rspec-core loaded, as that's the only context we currently have for testing rspec-expectations w/o rspec-core. But I'm not really sure it belongs there as this isn't really a "feature" and doesn't need to add noise to the test-unit cuke...but I'm not sure of a better way to write a test in a clean environment w/o rspec-core loaded. David, do you have any thoughts on this?


myronmarston commented Oct 23, 2010

Fix expect { ... }.to so that it has no dependency on rspec-core and can work outside of it.


dchelimsky commented Oct 23, 2010

Merged to master and 2-0-stable

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment