Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
JCR Content Parser 1.2.6, Testing Sling Mock 2.3.4
-
None
Description
loading test content from json is super simple and cool, but as soon as you have logical content in your project that is serialized in JCR-VLT format (xml), this forces you to:
- reproduce the application xml's content in a test json file,
- synchronize both file in later maintenance
we should allow tester to load mock content from an arbitrary path (not necessarily resource), and accept JCR-VLT format
Attachments
Issue Links
- breaks
-
SLING-10918 NPE in RRMockResourceResolverWrapper.getResource() when mixing JCR and default RR type
- Closed
-
SLING-10937 Resource in tested Sling Model not equal to Resource it was adapted from (RESOURCERESOLVER_MOCK)
- Closed
- causes
-
SLING-11252 RRMockResourceResolverWrapper supports no way of mocking searches
- Closed
- is blocked by
-
SLING-6592 JCR Content Parser
- Closed
- is related to
-
SLING-11455 ResourceResolver Mock: ResourceProvider implementation
- Closed
-
SLING-11548 sling-mock: Introduce RESOURCEPROVIDER_MOCK resource resolver type
- Closed
- relates to
-
SLING-7959 ContentParser: Complete support for (Extended) DocView
- Open
-
SLING-10753 sling-mock: Mount Folders of JSON or FileVault XML content
- Closed
-
SLING-6634 Use new Content Parser module in ContentLoader to support FileVault XML format (enhanced DocView)
- Open