multiple calls to .expects() should not assume next_call()

Issue #14 new
Kumar McMillan
repo owner created an issue

With this code:

{{{

!python

some_fake .expects('some_call').with_args('foo') .expects('some_call').with_args('bar') }}}

Th developer may want to check that either foo or bar were sent as arguments and in any order. Starting in 0.9.5 Fudge assumed that the above expectations were meant to be ordered but that was a bad assumption. http://farmdev.com/projects/fudge/index.html#changelog

Comments (0)

  1. Log in to comment