Verify without method call causes errors in other tests. about mockito HOT 8 CLOSED

Hi,

I wish this could be fixed. I think about it as a trade-off of elegant syntax.

Was the exception message any helpful for you to find the reason of the problem?

No, actually it took me quite a while to track down the issue.  Here is the 
exception
that I get:

org.mockito.exceptions.verification.WantedButNotInvoked: 
Wanted but not invoked:
testInterface.method2();

It seems like this problem could be fixed if you attached your MockingProgress 
object
to the actual mock object that the verification is done on (possibly with a 
map),
instead of keeping a static reference to it.  That way it would be lost when 
the test
is over, and not affect other tests. I don't know what all of the side effects 
of
this would be, but I almost always run into problems when I try to keep static 
data
while testing.

Oh, I see now. The exception is really confusing. Let me look at it.

I don't know how to fix it :( because in java there is no difference between:

verify(mock).foo();

and:

verify(mock);
mock.foo();

Do you have any ideas?

Is there something wrong with what I had suggested in Comment 2?  Other than 
that, I
can't think of anything that would allow you to keep the elegant syntax.

>That way it would be lost when the test is over, and not affect other tests.

I guess it wouldn't be lost unless I used weak references and system.gc() :)

I'm thinking of validating a state on mock creation. This means you would get 
much
better error message. I'll let you know when it's done.

Now, the state is validated on mock/spy creation so the exception message will 
be
much better. You might try it with the trunk version.

Fixed in trunk