Package org.mockito.plugins

Mockito plugins allow customization of behavior.

See: Description

Interface Summary

Interface	Description
AnnotationEngine	Configures test via annotations.
InstantiatorProvider	Deprecated since 2.15.4 because this internal class was leaking from the public API.
InstantiatorProvider2	Mockito will invoke this interface in order to fetch an instance instantiator provider.
MockitoPlugins	Instance of this interface is available via MockitoFramework.getPlugins().
MockMaker	The facility to create mocks.
MockMaker.TypeMockability	Carries the mockability information
PluginSwitch	Allows switching off the plugins that are discovered on classpath.
StackTraceCleanerProvider	An extension point to register custom StackTraceCleaner.

Package org.mockito.plugins Description

Mockito plugins allow customization of behavior. For example, it is useful for Android integration via dexmaker. See examples in docs for MockMaker.

The plugin mechanism of mockito works in a similar way as the ServiceLoader, however instead of looking in the META-INF directory, Mockito will look in mockito-extensions directory. The reason for that is that Android SDK strips jars from the META-INF directory when creating an APK.

For example :

1. Create implementation itself, for example org.awesome.mockito.AwesomeMockMaker that extends the MockMaker.
2. A file "mockito-extensions/org.mockito.plugins.MockMaker". The content of this file is exactly a one line with the qualified name: org.awesome.mockito.AwesomeMockMaker.

Note that if several mockito-extensions/org.mockito.plugins.MockMaker files exists in the classpath Mockito will only use the first returned by the standard ClassLoader.getResource mechanism.