[nicoddemus]

Fixes #639.

assert_has_calls and assert_has_awaits pass when the expected calls appear as a contiguous run anywhere in the actual calls (or in any order with any_order=True), but the introspection pytest-mock adds to their failures compares actual and expected calls position by position from the first call. It reports differences between calls that have nothing to do with each other:

m(1); m(2); m(3)
m.assert_has_calls([call(2), call(4)])

AssertionError: Calls not found.
Expected: [call(2), call(4)]
  Actual: [call(1), call(2), call(3)]

pytest introspection follows:

Args:
assert (1,) == (2,)
Args:
assert (2,) == (4,)
Args:
assert (3,) == ()

With this PR, the same failure is reported with the mock's own message only:

    def test_has_calls(mocker):
        m = mocker.stub()
        m(1); m(2); m(3)
>       m.assert_has_calls([mocker.call(2), mocker.call(4)])
E       AssertionError: Calls not found.
E       Expected: [call(2), call(4)]
E         Actual: [call(1), call(2), call(3)]

test_example.py:4: AssertionError

Pairing the calls correctly would need matching logic on top of the handling of every shape accepted as an expected call (call(...), (args, kwargs), (args,), (kwargs,), (name, args), ...), plus call names once mock_calls with child calls and magic methods is taken into account (#625). That handling has been the source of most of the recent bugs in this feature (#234, #617, #623). The mock's own message already lists both the expected and the actual calls, so this PR drops the introspection for these two assertions and keeps only the traceback hiding, like #642 did for assert_any_call and the count assertions.

This removes assert_has_calls_wrapper and _unpack_expected_call. The tests that checked the introspection now check that each accepted shape, calls= by keyword and any_order by position still fail with an AssertionError (the regressions fixed in #617 and #623) and without introspection.

🤖 Generated with Claude Code