cpython/Misc/NEWS.d/next/Library/2020-11-05-16-00-03.bpo-418...

Mock objects which are not unsafe will now raise an AttributeError if an attribute with the prefix asert, aseert,
or assrt is accessed, in addition to this already happening for the prefixes assert or assret.
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 13:04:38 -04:00			`Mock objects which are not unsafe will now raise an AttributeError if an attribute with the prefix asert, aseert,`
			`or assrt is accessed, in addition to this already happening for the prefixes assert or assret.`