RSpec: Undefined method `assert_difference' for ... (NoMethodError)
If you are using RSPEC, definitely 'change' should be the way to go. Here are two examples a negative and a positive one so you can have a sense of the syntax:
RSpec.describe "UsersSignups", type: :request do
describe "signing up with invalid information" do
it "should not work and should go back to the signup form" do
get signup_path
expect do
post users_path, user: {
first_name: "",
last_name: "miki",
email: "user@triculi",
password: "buajaja",
password_confirmation: "juababa"
}
end.to_not change{ User.count }
expect(response).to render_template(:new)
expect(response.body).to include('errors')
end
end
describe "signing up with valid information" do
it "should work and should redirect to user's show view" do
get signup_path
expect do
post_via_redirect users_path, user: {
first_name: "Julito",
last_name: "Triculi",
email: "[email protected]",
password: "worldtriculi",
password_confirmation: "worldtriculi"
}
end.to change{ User.count }.from(0).to(1)
expect(response).to render_template(:show)
expect(flash[:success]).to_not be(nil)
end
end
I'd better rewrite that using change
.
That's work for sure in RSpec 3.x, but probably in older versions as well.
context 'with event_type is available create event' do
let(:event_type) { EventType.where( name: 'visit_site').first }
it "changes event counter" do
expect { Event.fire_event(event_type, @sponge,{}) }.to change { Event.count }
end
end # with event_type is available create event
Make sure you include AssertDifference in spec/spec_helper.rb:
RSpec.configure do |config|
...
config.include AssertDifference
end
And put the assertion inside of an it
block:
it 'event count should change' do
assert_difference 'Event.count' do
...
end
end