Robolectric has many components which can be customized or replaced using an extension
mechanism based on
Historically, customizing Robolectric required subclassing
RobolectricTestRunner to override behavior at various ad-hoc extension points.
This mechanism is now deprecated. The Plugin API provides a number of well documented and
supported extension points allowing you to customize behavior for your organization's needs.
The interfaces listed below can be implemented with customizations suitable for your organization. To make your custom implementation visible to Robolectric, publish it as a service and include it in the test classpath.
- See Also:
- Google AutoService for a helpful way to define Java Services.
Interface Summary Interface Description NativeRuntimeLoaderLoads the Robolectric native runtime. SdkPicker SdkProviderA provider of known instances of
TestEnvironmentLifecyclePluginPlugin which allows behaviour extension in TestEnvironment. UsesSdkRepresents the contents of a
uses-sdkelement in an Android manifest file.
Class Summary Class Description SdkRepresents a unique build of the Android SDK.
Annotation Types Summary Annotation Type Description ExtensionPointMarks a component of Robolectric that may be replaced with a custom implementation.