public interface VerificationWithTimeout extends VerificationMode
VerificationMode
that allows combining existing verification modes with 'timeout'. E.g:
verify(mock, timeout(100).times(5)).foo();
verify(mock, timeout(100).never()).bar();
verify(mock, timeout(200).atLeastOnce()).baz();
See examples in javadoc for Mockito.verify(Object, VerificationMode)
Modifier and Type | Method and Description |
---|---|
VerificationMode |
atLeast(int minNumberOfInvocations)
Allows at-least-x verification withing given timeout.
|
VerificationMode |
atLeastOnce()
Allows at-least-once verification withing given timeout.
|
VerificationMode |
atMost(int maxNumberOfInvocations)
Deprecated.
Deprecated
validation with timeout combined with atMost simply does not make sense...
The test would have passed immediately in the concurrent environment
To avoid compilation erros upon upgrade the method is deprecated and it throws a "friendly reminder" exception. In future release we will remove timeout(x).atMost(y) from the API. Do you want to find out more? See issue 235 |
VerificationMode |
never()
Alias to times(0), see
times(int) |
VerificationMode |
only()
Allows checking if given method was the only one invoked.
|
VerificationMode |
times(int wantedNumberOfInvocations)
Allows verifying exact number of invocations within given timeout
|
verify
VerificationMode times(int wantedNumberOfInvocations)
verify(mock, timeout(100).times(2)).someMethod("some arg");
See examples in javadoc for Mockito
classwantedNumberOfInvocations
- wanted number of invocationsVerificationMode never()
times(int)
Verifies that interaction did not happen within given timeout. E.g:
verify(mock, timeout(100).never()).someMethod();
If you want to verify there were NO interactions with the mock
check out Mockito.verifyNoMoreInteractions(Object...)
See examples in javadoc for Mockito
class
VerificationMode atLeastOnce()
verify(mock, timeout(100).atLeastOnce()).someMethod("some arg");
Alias to atLeast(1)
See examples in javadoc for Mockito
class
VerificationMode atLeast(int minNumberOfInvocations)
verify(mock, timeout(100).atLeast(3)).someMethod("some arg");
See examples in javadoc for Mockito
classminNumberOfInvocations
- minimum number of invocations@Deprecated VerificationMode atMost(int maxNumberOfInvocations)
To avoid compilation erros upon upgrade the method is deprecated and it throws a "friendly reminder" exception.
In future release we will remove timeout(x).atMost(y) from the API.
Do you want to find out more? See issue 235
VerificationMode only()
verify(mock, only()).someMethod();
//above is a shorthand for following 2 lines of code:
verify(mock).someMethod();
verifyNoMoreInvocations(mock);
See also Mockito.verifyNoMoreInteractions(Object...)
See examples in javadoc for Mockito
class