|Modifier and Type||Method and Description|
Configures the test class instance for initialization of fields annotated with Mockito annotations like
Starts new mocking session! Creates new
Configures strictness of
@Incubating MockitoSessionBuilder initMocks(Object testClassInstance)
Mock. When this method is invoked it does not perform initialization of mocks on the spot! Only when
startMocking()is invoked then annotated fields will be initialized. Traditional API to initialize mocks, the
MockitoAnnotations.initMocks(Object)method has limited support for driving cleaner tests because it does not support configuring
Strictness. Want cleaner tests and better productivity? Migrate from
See code sample in
testClassInstance- test class instance that contains fields with Mockito annotations to be initialized. Passing
nullis permitted and will make the session use a default value. The current default is '
@Incubating MockitoSessionBuilder strictness(Strictness strictness)
MockitoSessioninstance. See examples in
nullis permitted and will make the session use a default value. The current default is
@Incubating MockitoSession startMocking() throws UnfinishedMockingSessionException
MockitoSessioninstance to initialize the session. At this point annotated fields are initialized per
initMocks(Object)method. When you are done with the session it is required to invoke
MockitoSession.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
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 session
UnfinishedMockingSessionException will be triggered.
See examples in