Closed spirin closed 1 month ago
When using mocks in large integration tests, it is very difficult to find places of unexpected function calls.
I suggest adding information about the location of the call.
Can you update a test too please? Possibly TestArgumentMatcherToPrintMismatch but maybe something else. Confirming that the test's own file base name is in the stack should be sufficient.
TestArgumentMatcherToPrintMismatch
Done
Summary
When using mocks in large integration tests, it is very difficult to find places of unexpected function calls.
Changes
I suggest adding information about the location of the call.
Motivation
Related issues