eranpeer
commented
9 years ago Hi, Fakeit doesn't support clearing only the recorded invocations. You can use mock.Reset() to completely reset the state of the mock to its initial state (as it was after ctor), but then you will have to re-stub the methods you're about to call.
I will add support for a clearing the recorded invocations in the next few days. Meantime here is what you can do:
struct AnInterface {
virtual int func(int) = 0;
};
Mock<AnInterface> mock;
When(Method(mock, func)).AlwaysReturn(0);
AnInterface& obj = mock.get();
obj.func(1);
// Verify exactly one invocation of obj.func(1)
Verify(Method(mock, func).Using(1)).Once();
obj.func(2);
// Verify one invocation of obj.func(any argument) followed by obj.func(2)
Verify(Method(mock, func) + Method(mock, func).Using(2)).Once();
obj.func(3);
// Verify 2 invocations of obj.func(any argument) followed by obj.func(3)
Verify(2 * Method(mock, func) + Method(mock, func).Using(3)).Once();
obj.func(4);
// Verify 3 invocations of obj.func(any argument) followed by obj.func(4)
Verify(3 * Method(mock, func) + Method(mock, func).Using(4)).Once();I hope this helps your situation.
sleep-deprived
Hi,
First let me start by saying that this is a great framework. I ran across it a few hours ago and already I was able to use it in a few unit tests, eliminating some self made mocking classes. It also seems really robust and feature-rich.
I would like to propose / request a few features. I'll open a separate issue for each.
For this request, there might already be an implemented solution, but I couldn't find it. I also seem to not fully understand the conditions in which Verify() fails - since the order of calls to the various Verify*() macros matters.
We have a few unit tests each representing a flow. I want to be able to check the invocation of methods in my mocks after every step of the flow.
I use the Verify().Once() to make sure the correct method and parameters were called, and immediately VerifyNoOtherInvocations(mock) to make sure nothing else was called.
What I'd like to do then is to 'clear the table' for the next step, so I can once again call Once() (with different parameters, if needed) and VerifyNoOtherInvocations().
Doing just that seems to work, unless the same parameters repeat themselves, in which case Verify().Once() complains that the method was called more than once. I'd like to avoid the need for counting the calls by myself, especially since adding a step in the middle of the flow might require me to change everything.
What I suggest is a syntax such as: Method(mock, methodName).ResetInvocations()
This will cause the internal structs to delete all the previously recorded invocations.
Do you have another solution? Or if not, is it possible to add it for the next version?
Thanks.