*Mockito verboseLogging, plus GuiceBerry hints*

Want to see your mock activity?  Do something like this:

mock(SharingJsonService.FutureInterface.class,
    withSettings().verboseLogging());

Also: Injecting a GuiceBerry mock?  Reset it in a teardown!

There's probably a better way to do this, but.....  I created a Mock inside a GuiceBerry module, then injected it into the test class.

There were two tests that mocked the same method, the second test would blow up because it saw the previous stub, and returned null for the second invocation instead of re-stubbing.

Adding a Mockito.reset(...) on the injected value fixes that.

Thanks to verbose logging I was able to figure that out.

Phew, time for bed.




#googplus

#googplus