Closed GoogleCodeExporter closed 9 years ago
Thanks we'll take a look.
Contributions are welcome :)
Original comment by szcze...@gmail.com
on 27 Jan 2014 at 6:58
Hierarchy : MockingProgressImpl > OngoingStubbingImpl > InvocationContainerImpl
> DefaultRegisteredInvocations > LinkedList<Invocation> invocations
I think DefaultRegisteredInvocations should expose a clear() method to cleanup
invocations. But the method Mockito.reset() calls resetOngoingStubbing() that
set iOngoingStubbing to null. So I don't understand why invocations are
retained in memory ?
Original comment by Grosset...@gmail.com
on 27 Jan 2014 at 8:41
In order to verify them, I believe the git repo has a fix for that allowing to
create mocks for stubbing only, in the settings API.
Would that work for you ?
Cheers,
Brice
Original comment by brice.du...@gmail.com
on 4 Mar 2014 at 9:22
There :
https://github.com/mockito/mockito/blob/master/src/org/mockito/MockSettings.java
#L233
Original comment by brice.du...@gmail.com
on 4 Mar 2014 at 9:25
Hi Brice,
I didn't know about that feature... but that would not work for us because we
need to verify the number of invocations.
If you want I can validate that I can't reproduce this issue when using
stubOnly() ?
Original comment by Grosset...@gmail.com
on 4 Mar 2014 at 12:35
nope it has been done already :)
This is obviously one of the trade-off of the verification after approach.
Maybe Easymock can work better for you in this case.
Original comment by brice.du...@gmail.com
on 12 Mar 2014 at 11:03
Original comment by brice.du...@gmail.com
on 5 Aug 2014 at 1:27
Original issue reported on code.google.com by
Grosset...@gmail.com
on 23 Jan 2014 at 5:17