Piotr Wlodarek
2008-Jul-15 08:00 UTC
[rspec-users] should_receive - how to allow multiple calls
code: info( ''attempting to sign in'' ) # I want to test it # ... info( ''signed in'' ) # I don''t care about it spec: @scraper.should_receive( :info ).with( ''attempting to sign in'' ).at_least( 1 ).times result: expected :info with ("attempting to sign in") but received it with ("signed in") question: This is strange. How to test if method was called with specific argument AND don''t care about other possible calls of that method? -- Posted via http://www.ruby-forum.com/.
David Chelimsky
2008-Jul-15 11:58 UTC
[rspec-users] should_receive - how to allow multiple calls
On Tue, Jul 15, 2008 at 3:00 AM, Piotr Wlodarek <lists at ruby-forum.com> wrote:> code: > > info( ''attempting to sign in'' ) # I want to test it > # ... > info( ''signed in'' ) # I don''t care about it > > > spec: > > @scraper.should_receive( :info ).with( ''attempting to sign in'' > ).at_least( 1 ).times > > > result: > expected :info with ("attempting to sign in") but received it with > ("signed in") > > > question: > This is strange.This is normal :) It''s how most mock frameworks work because most of the time we want to know if unexpected calls start showing up.> How to test if method was called with specific argument > AND don''t care about other possible calls of that method?@scraper.stub!(:info) @scraper.should_receive(:info).with("attempting to sign in") Cheers, David> -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >