Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
None
-
None
Description
Found some typos and inconsistencies on Sling Mocks, OSGi Mocks & Resource Resolver Mock documentation pages.
Sling Mocks http://sling.apache.org/documentation/development/sling-mock.html
AdpaterManager implementation for registering adapter factories and resolving adaptions
The implementation is thread-safe so it can be used in parallel running unit tests
It is possible to set request data to simulate a certian Sling HTTP request
Additional services like MockModelAdapterFactory and MimeTypeService
The following features are not supported:
Additional features provided:
SlingContext JUnit Rule for easily setting up a Sling Mock environment in your JUnit testcases
ContentLoader supports importing JSON...
Depending on the type an underlying JCR repository is used or not, and the data ist stored in-memory or in a real repository.
If you use the SlingContext Junit rule this is done automatically for you.
With the ContentLoader it is possible to import a binary file stored in the classpath beneath the unit tests. The data is stored usig a nt:file/nt:resource or nt:resource node type.
OSGi Mocks http://sling.apache.org/documentation/development/osgi-mock.html
Call lifecyle methods for activating, deactivating or modifying SCR components
Service and bundle listener implementation
Resource Resolver Mock http://sling.apache.org/documentation/development/resourceresolver-mock.html
Mimicks transactions using via commit()/revert() methods
OSGi events for adding/changing/removing resources
Querying with qeuryResources/findResources not supported (always returns empty result set)
Sling Mapping is not supported
Resolving resouce super types
Other pages like JCR Mocks http://sling.apache.org/documentation/development/jcr-mock.html are free of typos.