Is your feature request related to a problem? Please describe.
When you assert the number of calls for some method in complex code and the assertions fail it might be hard from which part of the code these calls come.
Describe the solution you'd like
Store the stack traces for each call and upon failure of the assertion display them together with "-> call with arguments ..." messages.
Describe alternatives you've considered
No idea.
Additional context
A possible problem is how to present this information in order to avoid overwhelming the dev with too much information... Possible there could be either env. variable or a flag that would enable such behavior.
Is your feature request related to a problem? Please describe.
When you assert the number of calls for some method in complex code and the assertions fail it might be hard from which part of the code these calls come.
Describe the solution you'd like
Store the stack traces for each call and upon failure of the assertion display them together with "-> call with arguments ..." messages.
Describe alternatives you've considered
No idea.
Additional context
A possible problem is how to present this information in order to avoid overwhelming the dev with too much information... Possible there could be either env. variable or a flag that would enable such behavior.