forked from datamapper/dm-core
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Changed usage of be_true and be_false in specs to be(true) and be(false)
* This is due to a change in RSpec where be_true now passes with any object, except false or nil. be_false will pass with the false or nil, and fail with everything else. More information on the change: https://rspec.lighthouseapp.com/projects/5645/tickets/931 While I can understand why this change was made, any place in the specs where be_true and be_false was specified, the intention was to assert that either true or false *only* was being returned; we wanted the spec to fail if nil or any other object was returned.
- Loading branch information
Showing
24 changed files
with
371 additions
and
369 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.