[issue21692] Wrong order of expected/actual for assert_called_once_with

2014-06-09 Thread Fei Long Wang
Fei Long Wang added the comment: Okay, I can see your point now. Thanks for the clarification. -- ___ Python tracker <http://bugs.python.org/issue21692> ___ ___

[issue21692] Wrong order of expected/actual for assert_called_once_with

2014-06-08 Thread Fei Long Wang
Fei Long Wang added the comment: IMHO, the trace should be: AssertionError: Expected call: some_method('foo', 'bar') Actual call: some_method('foo', 'baz') instead of below: AssertionError: Expected call: some_method('foo

[issue21692] Wrong order of expected/actual for assert_called_once_with

2014-06-08 Thread Fei Long Wang
New submission from Fei Long Wang: >>> m=mock.Mock() >>> m.some_method('foo', 'bar') >>> m.some_method.assert_called_once_with('foo', 'bar') >>> m.some_method.assert_called_once_with('foo', 'baz')