mirror of
https://github.com/python/cpython.git
synced 2025-08-03 00:23:06 +00:00
bpo-41877 Check for asert, aseert, assrt in mocks (GH-23165)
Currently, a Mock object which is not unsafe will raise an AttributeError if an attribute with the prefix assert or assret is accessed on it. This protects against misspellings of real assert method calls, which lead to tests passing silently even if the tested code does not satisfy the intended assertion. Recently a check was done in a large code base (Google) and three more frequent ways of misspelling assert were found causing harm: asert, aseert, assrt. These are now added to the existing check.
This commit is contained in:
parent
133aa2d581
commit
4662fa9bfe
3 changed files with 14 additions and 3 deletions
|
@ -1598,14 +1598,23 @@ class MockTest(unittest.TestCase):
|
|||
#Issue21238
|
||||
def test_mock_unsafe(self):
|
||||
m = Mock()
|
||||
msg = "Attributes cannot start with 'assert' or 'assret'"
|
||||
msg = "Attributes cannot start with 'assert' or its misspellings"
|
||||
with self.assertRaisesRegex(AttributeError, msg):
|
||||
m.assert_foo_call()
|
||||
with self.assertRaisesRegex(AttributeError, msg):
|
||||
m.assret_foo_call()
|
||||
with self.assertRaisesRegex(AttributeError, msg):
|
||||
m.asert_foo_call()
|
||||
with self.assertRaisesRegex(AttributeError, msg):
|
||||
m.aseert_foo_call()
|
||||
with self.assertRaisesRegex(AttributeError, msg):
|
||||
m.assrt_foo_call()
|
||||
m = Mock(unsafe=True)
|
||||
m.assert_foo_call()
|
||||
m.assret_foo_call()
|
||||
m.asert_foo_call()
|
||||
m.aseert_foo_call()
|
||||
m.assrt_foo_call()
|
||||
|
||||
#Issue21262
|
||||
def test_assert_not_called(self):
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue