Open Ellisande opened 8 years ago
I think I've come up with a better pattern than what you see in most mocking frameworks for this that will come out cleaner and more consistent. Building a prototype implementation and then I'll open a discussion ticket about the pattern.
What kind of issue is this? (bug, feature, etc)
Feature
What is the proposed change?
Have mock function keep track of their call history so they can be verified.
What was the old behavior, if any?
No current behavior.
Why will this be beneficial?
It will allow people to test mocks that don't return output more efficiently.