public interface MockitoRule
extends org.junit.rules.MethodRule
strictness(Strictness) which automatically
detects stubbing argument mismatches and is planned to be the default in Mockito v3.
Since Mockito 2.1.0, JUnit rule emits stubbing warnings and hints to System output (see MockitoHint).
The JUnit rule can be used instead of MockitoJUnitRunner.
It requires JUnit at least 4.7.
The rule adds following behavior:
silent().
However, we would really like to know why do you wish to silence the warnings!
See also MockitoHint.
Mock,
so that explicit usage of MockitoAnnotations.openMocks(Object) is not necessary.
Mocks are initialized before each test method.
Mockito.validateMockitoUsage().
strictness(Strictness) configured to Strictness.STRICT_STUBS.
It drives cleaner tests and improves debugging experience.
The only reason this feature is not turned on by default
is because it would have been an incompatible change
and Mockito strictly follows semantic versioning.
public class ExampleTest {
//Creating new rule with recommended Strictness setting
@Rule public MockitoRule rule = MockitoJUnit.rule().strictness(Strictness.STRICT_STUBS);
@Mock
private List list;
@Test
public void shouldDoSomething() {
list.add(100);
}
}
MockitoSession API is intended to offer cleaner tests and improved debuggability
to users that cannot use Mockito's built-in JUnit support (runner or the rule).| Modifier and Type | Method and Description |
|---|---|
MockitoRule |
silent()
Rule will not report stubbing warnings during test execution.
|
MockitoRule |
strictness(Strictness strictness)
The strictness, especially "strict stubs" (
Strictness.STRICT_STUBS)
helps debugging and keeping tests clean. |
MockitoRule silent()
strictness(Strictness) with Strictness.LENIENT.
Please give us feedback about the stubbing warnings of JUnit rules
by commenting on GitHub issue 769.
It's a new feature of Mockito 2.1.0. It aims to help debugging tests.
We want to make sure the feature is useful.
We would really like to know why do you wish to silence the warnings!
See also MockitoHint.
Example:
public class ExampleTest {
@Rule
public MockitoRule rule = MockitoJUnit.rule().silent();
}
@Incubating MockitoRule strictness(Strictness strictness)
Strictness.STRICT_STUBS)
helps debugging and keeping tests clean.
It's a new feature introduced in Mockito 2.3.
Other levels of strictness - "warn" - (Strictness.WARN)
and "lenient" (silent()) strictness were already present in Mockito 2.1.0.
Version 2.3.0 introduces "strict stubs" (Strictness.STRICT_STUBS).
public class ExampleTest {
@Rule
public MockitoRule rule = MockitoJUnit.rule().strictness(Strictness.STRICT_STUBS);
}
Strictness to learn how strictness influences the behavior of the JUnit rule.
See Strictness.STRICT_STUBS to learn why is it recommended to use "strict stubbing".
It is possible to tweak the strictness per test method.
Why would you need it? See the use cases in Javadoc for PotentialStubbingProblem class.
In order to tweak strictness per stubbing see Mockito.lenient(), per mock see MockSettings.lenient().
public class ExampleTest {
@Rule
public MockitoRule rule = MockitoJUnit.rule().strictness(Strictness.STRICT_STUBS);
@Test public void exampleTest() {
//Change the strictness level only for this test method
//Useful for edge cases (see Javadoc for PotentialStubbingProblem class)
mockito.strictness(Strictness.LENIENT);
//remaining test code
}
}