org.mockito.verification
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();
This is similar to after() except this assertion will immediately pass if it becomes true at any point,
whereas after() will wait the full period. Assertions which are consistently expected to be initially true and potentially become false
are deprecated below, and after() should be used instead.
See examples in javadoc for Mockito.verify(Object, VerificationMode)
| Modifier and Type | Method and Description |
|---|---|
VerificationMode |
atLeast(int minNumberOfInvocations)
Allows at-least-x verification within given timeout.
|
VerificationMode |
atLeastOnce()
Allows at-least-once verification within given timeout.
|
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
|
description, verifyVerificationMode times(int wantedNumberOfInvocations)
verify(mock, timeout(100).times(2)).someMethod("some arg");
See examples in javadoc for Mockito classwantedNumberOfInvocations - wanted number of invocationsVerificationMode 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 invocationsVerificationMode only()
verify(mock, only()).someMethod();
//above is a shorthand for following 2 lines of code:
verify(mock).someMethod();
verifyNoMoreInteractions(mock);
See also Mockito.verifyNoMoreInteractions(Object...)
See examples in javadoc for Mockito class