Lines Matching refs:mock_calls

147 :attr:`~Mock.mock_calls` attribute records all calls
155     >>> mock.mock_calls
158 If you make an assertion about ``mock_calls`` and any unexpected methods
164 ``mock_calls``:
167     >>> mock.mock_calls == expected
176     >>> m.mock_calls[-1] == call.factory(important=False).deliver()
223     >>> mock.mock_calls
225     >>> mock.mock_calls == expected
566 Using :attr:`~Mock.mock_calls` we can check the chained call with a single
568 several entries in ``mock_calls``. We can use :meth:`call.call_list` to create
573     >>> assert mock_backend.mock_calls == call_list
1172 however we can use :attr:`~Mock.mock_calls` to achieve the same effect.
1174 Because mocks track calls to child mocks in ``mock_calls``, and accessing an
1177 in order, in the ``mock_calls`` of the parent:
1188     >>> manager.mock_calls
1192 the ``mock_calls`` attribute on the manager mock:
1195     >>> manager.mock_calls == expected_calls
1200 attaching calls will be recorded in ``mock_calls`` of the manager. ::
1211     >>> manager.mock_calls
1221 :attr:`~Mock.mock_calls` then the assert succeeds.