MockitoSession objects.
See the documentation and examples in Javadoc for MockitoSession.- Since:
- 2.7.0
-
Method Summary
Modifier and TypeMethodDescriptionAdds the test class instance for initialization of fields annotated with Mockito annotations likeMock.Adds the test class instances for initialization of fields annotated with Mockito annotations likeMock.logger(MockitoSessionLogger logger) Configures logger used byMockitoSessionfor emitting warnings when finishing the session.Configures the name of theMockitoSessioninstance.Starts new mocking session! Creates newMockitoSessioninstance to initialize the session.strictness(Strictness strictness) Configures strictness ofMockitoSessioninstance.
-
Method Details
-
initMocks
Adds the test class instance for initialization of fields annotated with Mockito annotations likeMock. When this method is invoked it does not perform initialization of mocks on the spot! Only whenstartMocking()is invoked then annotated fields will be initialized. Traditional API to initialize mocks, theMockitoAnnotations.openMocks(Object)method has limited support for driving cleaner tests because it does not support configuringStrictness. Want cleaner tests and better productivity? Migrate fromMockitoAnnotations.openMocks(Object)toMockitoSession!This method may be called multiple times to add multiple, e.g. nested, test class instances.
See code sample in
MockitoSession.- Parameters:
testClassInstance- test class instance that contains fields with Mockito annotations to be initialized. Passingnullis permitted but will be ignored.- Returns:
- the same builder instance for fluent configuration of
MockitoSession. - Since:
- 2.7.0
-
initMocks
Adds the test class instances for initialization of fields annotated with Mockito annotations likeMock.In most scenarios, you only need to init mocks on a single test class instance. This method is useful for advanced framework integrations (like JUnit Jupiter), when a test uses multiple, e.g. nested, test class instances.
This method calls
initMocks(Object)for each passed test class instance.- Parameters:
testClassInstances- test class instances that contains fields with Mockito annotations to be initialized. Passingnullor an empty array is permitted but will be ignored.- Returns:
- the same builder instance for fluent configuration of
MockitoSession. - Since:
- 2.15.0
- See Also:
-
name
Configures the name of theMockitoSessioninstance.The name is used to output hints when finishing a session.
This method is intended to be used by framework integrations, e.g. JUnit. When building a
MockitoSessionfor direct use, users are not expected to call it.- Parameters:
name- ofMockitoSessioninstance. Passingnullis permitted and will make the session use a default value. The current default is the name of the last test class instance passed toinitMocks(Object)orinitMocks(Object...), if available; otherwise,"<Unnamed Session>"is used.- Returns:
- the same builder instance for fluent configuration of
MockitoSession. - Since:
- 2.15.0
- See Also:
-
strictness
Configures strictness ofMockitoSessioninstance. See examples inMockitoSession.- Parameters:
strictness- forMockitoSessioninstance. Passingnullis permitted and will make the session use a default value. The current default isStrictness.STRICT_STUBS.- Returns:
- the same builder instance for fluent configuration of
MockitoSession. - Since:
- 2.7.0
-
logger
Configures logger used byMockitoSessionfor emitting warnings when finishing the session.Please note that the use of strict stubs is recommended over emitting warnings because warnings are easily ignored and spoil the log output. Instead of using this method, please consider setting strictness with
strictness(Strictness).- Parameters:
logger- for warnings emitted when finishingMockitoSession. Passingnullis permitted and will make the session use a default value. By default, warnings will be logged to the console.- Returns:
- the same builder instance for fluent configuration of
MockitoSession. - Since:
- 2.15.0
- See Also:
-
startMocking
Starts new mocking session! Creates newMockitoSessioninstance to initialize the session. At this point annotated fields are initialized perinitMocks(Object)method. When you are done with the session it is required to invokeMockitoSession.finishMocking(). This will trigger stubbing validation, cleaning up the internal state like removal of internal listeners.Mockito tracks created sessions internally and prevents the user from creating new sessions without using
MockitoSession.finishMocking(). When you run tests concurrently in multiple threads, it is legal for each thread to have single active Mockito session. When you attempt to start new session in a thread that already has an unfinished sessionUnfinishedMockingSessionExceptionwill be triggered.See examples in
MockitoSession.- Returns:
- new
MockitoSessioninstance - Throws:
UnfinishedMockingSessionException- when previous session was not concluded withMockitoSession.finishMocking()- Since:
- 2.7.0
-