[rspec-users] Expectation ordering
dchelimsky at gmail.com
Tue Oct 7 10:15:12 EDT 2008
On Tue, Oct 7, 2008 at 7:59 AM, Ashley Moran
<ashley.moran at patchspace.co.uk> wrote:
> Can I still rely on this RSpec behaviour?
> I've got a spec for a TCP socket client:
> it "should do things in a sane order" do
> @socket.should_receive(:write) do
> @socket.should_receive(:read) do
> But this passes, where I was expecting it to fail:
> def update_news_feeds
> socket = TCPSocket.new(@server, @port)
> Has this form of expectation ordering been removed?
As far as I know this form of expectation ordering was never
supported. If you've seen documentation that suggests it should be,
please point me to it so I can resolve the discrepancy.
Ordering in rspec mocks is managed with the #ordered method:
See http://rspec.info/documentation/mocks/message_expectations.html -
almost all the way down the page.
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users