search for: should_not_b

Hi! I just stumbled over a possible bug in 0.7.5.1: `1.should_not_be == 1` does not fail. I took a look into the code and figured out, that this is caused by Not.be() using :no_arg instead of :___no_arg. The expected argument of the method be() in Not is passed from should_not_be() with :___no_arg. Not.be() is marked with "Gone for 0.9", so I assume tha...

...hould add a record" do post :edit_or_create, :user => {:login => ''joeschmoe'', :email => ''joe at shmoe.com'', :email_confirmation => ''joe at shmoe.com'', :full_name => ''Joe Schmoe''} assigns[:user].should_not_be_nil assigns[:user].new_record?.should_not_be(true) flash[:notice].should_match(/user added/) response.should_be_redirect puts "redirecting to #{response.redirect_url}" puts "this response was #{response.redirect?}" controller.should_redirect_to ...

There''s another quirk I wanted to bring up. It''s about the failure message with should_equal and should_be. x.should_equal 2 a.should_not_be nil When they fail they yield messages like: 1 should equal 2 nil should not be nil When I''m caught off guard, which can be often, these messages confuse me. 1 should equal 2? No it shouldn''t. nil should not be nil? But they are the same! You get my drift? When taken...

....tmbundle/Snippets/exactly.tmSnippet RSpec.tmbundle/Snippets/It.tmSnippet RSpec.tmbundle/Snippets/mock.tmSnippet RSpec.tmbundle/Snippets/once.tmSnippet RSpec.tmbundle/Snippets/Require spec_helper.tmSnippet RSpec.tmbundle/Snippets/response_should_be_success.tmSnippet RSpec.tmbundle/Snippets/response_should_not_be_success.tmSnippet RSpec.tmbundle/Snippets/Set Controller for Spec.tmSnippet RSpec.tmbundle/Snippets/setup.tmSnippet RSpec.tmbundle/Snippets/should ==.tmSnippet RSpec.tmbundle/Snippets/should =~.tmSnippet RSpec.tmbundle/Snippets/should eql.tmSnippet RSpec.tmbundle/Snippets/should_be.tmSnippet RSpec...