| Package | Description |
|---|---|
| org.mockito |
Mockito is a mock library for java - see Mockito class for for usage.
|
| org.mockito.configuration |
Mockito configuration utilities
|
| org.mockito.internal |
Internal classes, not to be used by clients.
|
| org.mockito.internal.configuration |
Mockito configuration
|
| org.mockito.internal.creation |
Mock object creation.
|
| org.mockito.internal.debugging |
Whatever helps in debugging failed tests
|
| org.mockito.internal.listeners | |
| org.mockito.internal.matchers |
Argument matchers for verification and stubbing.
|
| org.mockito.internal.matchers.apachecommons |
Argument matchers that use Apache Commons Lang reflection-equality.
|
| org.mockito.internal.progress |
Mocking progress stateful classes.
|
| org.mockito.internal.stubbing.answers |
Answers for stubbed calls
|
| Class and Description |
|---|
| Answers
Enumeration of pre-configured mock answers
|
| ArgumentCaptor
Use it to capture argument values for further assertions.
|
| BDDMockito.BDDMyOngoingStubbing
See original
OngoingStubbing |
| BDDMockito.BDDStubber
See original
Stubber |
| InOrder
Allows verification in order.
|
| Matchers
Allow flexible verification or stubbing.
|
| Mockito
|
| MockSettings
Allows mock creation with additional mock settings.
|
| ReturnValues
Deprecated.
Instead, please use
Answer interface
In rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent. Why it is deprecated? ReturnValues is being replaced by Answer for better consistency & interoperability of the framework. Answer interface has been in Mockito for a while and it has the same responsibility as ReturnValues. There's no point in mainting exactly the same interfaces. Configures return values for an unstubbed invocation
Can be used in |
| Class and Description |
|---|
| ReturnValues
Deprecated.
Instead, please use
Answer interface
In rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent. Why it is deprecated? ReturnValues is being replaced by Answer for better consistency & interoperability of the framework. Answer interface has been in Mockito for a while and it has the same responsibility as ReturnValues. There's no point in mainting exactly the same interfaces. Configures return values for an unstubbed invocation
Can be used in |
| Class and Description |
|---|
| InOrder
Allows verification in order.
|
| MockSettings
Allows mock creation with additional mock settings.
|
| Class and Description |
|---|
| ReturnValues
Deprecated.
Instead, please use
Answer interface
In rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent. Why it is deprecated? ReturnValues is being replaced by Answer for better consistency & interoperability of the framework. Answer interface has been in Mockito for a while and it has the same responsibility as ReturnValues. There's no point in mainting exactly the same interfaces. Configures return values for an unstubbed invocation
Can be used in |
| Class and Description |
|---|
| MockSettings
Allows mock creation with additional mock settings.
|
| Class and Description |
|---|
| MockitoDebugger |
| Class and Description |
|---|
| MockSettings
Allows mock creation with additional mock settings.
|
| Class and Description |
|---|
| ArgumentMatcher
Allows creating customized argument matchers.
|
| Class and Description |
|---|
| ArgumentMatcher
Allows creating customized argument matchers.
|
| Class and Description |
|---|
| MockSettings
Allows mock creation with additional mock settings.
|
| Class and Description |
|---|
| ReturnValues
Deprecated.
Instead, please use
Answer interface
In rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent. Why it is deprecated? ReturnValues is being replaced by Answer for better consistency & interoperability of the framework. Answer interface has been in Mockito for a while and it has the same responsibility as ReturnValues. There's no point in mainting exactly the same interfaces. Configures return values for an unstubbed invocation
Can be used in |
Copyright © 2016. All rights reserved.