R. David Murray added the comment:
But the actual call that you made in your example was some_method('foo', 'bar').
Given that we conventionally write unittest assertions with the actual result
first and the expected result second (assertEqual(actual, expected), it might
be less confusing if the message was:
AssertionError: Actual call: some_method('foo', 'bar')
Expected call: some_method('foo', 'baz')
But since the actual call does appear in the assert call that generates the
assertionError, it is not obvious that this would actually be a better order.
----------
nosy: +r.david.murray
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue21692>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
