New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Puzzling behavior with eventually and rspec be_nil matcher #25

Open

ziobrando opened this issue Jan 9, 2013 · 0 comments

ziobrando commented Jan 9, 2013

I found an odd behavior when using eventually and should_not be_nil.

it "should work with be_nil" do
    found = "X"
    eventually {
      found.should_not be_nil
    }
end

Error message is:

Expected found.should_not(be_nil), but
found is "X"
be_nil is #<RSpec::Matchers::BuiltIn::BeNil:0x007ff531aea8e8
@expected=nil>

Am I doing anything wrong?

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