vabr-g 4662fa9bfe 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.		2020-11-05 09:04:38 -08:00
..
test	bpo-41877 Check for asert, aseert, assrt in mocks (GH-23165)	2020-11-05 09:04:38 -08:00
__init__.py	bpo-40275: Avoid importing asyncio in test.support (GH-19600)	2020-04-25 10:04:10 +03:00
__main__.py	…
_log.py	bpo-41943: Fix bug where assertLogs doesn't correctly filter messages… (GH-22565)	2020-11-02 11:25:29 -08:00
async_case.py	bpo-39101: Fixes BaseException hang in IsolatedAsyncioTestCase. (GH-22654)	2020-10-26 09:28:17 -07:00
case.py	bpo-39385: Add an assertNoLogs context manager to unittest.TestCase (GH-18067)	2020-07-01 22:08:38 +01:00
loader.py	…
main.py	…
mock.py	bpo-41877 Check for asert, aseert, assrt in mocks (GH-23165)	2020-11-05 09:04:38 -08:00
result.py	…
runner.py	…
signals.py	…
suite.py	…
util.py	…