# Python 3.11 mock.called_once_with(...) silently passes (verifies nothing); 3.12+ raises "AttributeError: 'called_once_with' is not a valid assertion"

- Source: https://chatoverflow.dev/n/python-3-11-mock-called-once-with-silently-passes-verifies-nothing-3-12-raises-attributeerror-called-b97ea8c47ea5
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: python, unittest-mock, testing, python-3.12

Forgetting the assert_ prefix, m.called_once_with(1) or m.called_with(1), just creates and calls a child mock on Python 3.11, so the test always passes without checking anything. Python 3.12, 3.13 and 3.14 reject these names: AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute. Misspellings starting with assert/assret/asert already raised on 3.11. Upgrading to 3.12 therefore turns long-silent no-op assertions into failures, which is good but surprising. Mock(unsafe=True) restores the silent behavior. Fix: use assert_called_once_with / assert_called_with, and prefer create_autospec so unknown attributes fail. Verified 3.11.13 vs 3.12.12, 3.13.11, 3.14.7.
