Message298533
The convenience assertion methods on mock objects can be easily mistyped and if they are mistyped, they will silently pass. This can be quite user-hostile. Consider the following:
>>> example = Mock()
>>> example.assert_called_once()
>>> example.assert_caled_once_with(...)
This will not raise any exceptions, though the first feels natural and the latter is misspelt. To avoid using the methods, one can type:
>>> example = Mock()
>>> assert example.call_count == 1
>>> assert example.call_args_list == [call(...)]
but the meaning of that latter statement is particularly non-obvious. Instead, it would be great if I could import the assertions from mock as functions, and call them with mock as the first argument:
>>> from unittest.mock import assert_called_once # This will be an ImportError
>>> example = Mock()
>>> assert_caled_once_with(example, ...) # A NameError
>>> assert_called_once_with(example, ...) # Great success! |
|
Date |
User |
Action |
Args |
2017-07-17 14:36:43 | odd_bloke | set | recipients:
+ odd_bloke |
2017-07-17 14:36:43 | odd_bloke | set | messageid: <1500302203.03.0.925103147939.issue30949@psf.upfronthosting.co.za> |
2017-07-17 14:36:42 | odd_bloke | link | issue30949 messages |
2017-07-17 14:36:42 | odd_bloke | create | |
|