title: Rspec NoMethodError: undefined method `call', yet everything works via rails console
body: <p>I'm a rails/rspec newb trying to learn.  I've setup the following data model (excerpt)</p>
  
  <pre><code>t.string :foo
  t.string :bar
  t.date :future_date
  </code></pre>
  
  <p>and I have a web form to create these entries associated with a user, similar to the microposts in this <a href="http://ruby.railstutorial.org/chapters/user-microposts#top" rel="nofollow">rails tutorial</a>.  The web form looks like this (excerpt):</p>
  
  <pre><code>&lt;%= f.label :foo %&gt;
  &lt;%= f.text_field :foo %&gt;
  &lt;%= f.label :bar %&gt;
  &lt;%= f.text_field :bar %&gt;
  &lt;%= f.date_select :future_date %&gt;
  </code></pre>
  
  <p>with a button, "Create", that initiates the post.  Everything seems to work fine via rails console; the web form displays correctly, the entries are created correctly, the database is being populated correctly.  However, when I run rspec I get </p>
  
  <pre><code>NoMethodError:
    undefined method `call' for #&lt;RSpec::Expectations::ExpectationTarget:0x0000000492b7c0&gt;
  </code></pre>
  
  <p>Here is the relevant request spec (excerpt):</p>
  
  <pre><code>it "should not create a foobar" do
    expect { click_button "Create" }.should_not change(Foobar, :count)
  end
  </code></pre>
  
  <p>In other words, click "Create" with no info filled in.  I have a similar example later with info filled in but nearly the same click_button that also throws this error (should change .by(1)).  I have similar click_button tests working fine for the user creation portion (nothing/something entered) which, other than future_date, is very similar.  That, plus something I ran across in my endless googling, leads me to believe the date is somehow to blame, perhaps an inconsistency in versions or something.  Especially since in actual use everything is working fine.  This is with ruby 1.9.3, Rails 3.2.6, and Rspec 2.11.1.  Any insight is very much appreciated.</p>