-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getCall is not working correctly #4
Comments
Right, checking There is another thing need to consider, there is no For OOD, you might consider to implement an interface for Wrapper called Call. For sure this is an option. |
Over the long term, I think that creating a new class |
Hi, By the way, I highly recommend you to |
I think that
getCall
is not actually returning a call, but rather returning a queued spy/stub. Every time a new spy or stub is created, a new item is added to the queue, and this new item is what's returned bygetCall
. What is supposed to happen is thatgetCall
should return the execution of a particular spy or stub. Perhapsargs_list
should be used bygetCall
?The text was updated successfully, but these errors were encountered: