You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2022/09/02 11:17:00 UTC
[jira] [Closed] (SLING-11455) ResourceResolver Mock: ResourceProvider implementation
[ https://issues.apache.org/jira/browse/SLING-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-11455.
----------------------------------
> ResourceResolver Mock: ResourceProvider implementation
> ------------------------------------------------------
>
> Key: SLING-11455
> URL: https://issues.apache.org/jira/browse/SLING-11455
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing ResourceResolver Mock 1.4.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> ResourceResolver Mock currently supports only directly creating a mocked ResourceResolver instances, which is fine for most testing use cases. however, since introduction of SLING-5922 we allow mounting of additional test resources into the resource tree via FSResourceProvider, and are currently using a rough hand-build intergration of MockResourceResolver and this resource provider. this has some flaws and unwanted side-effects, SLING-10937 is one of it.
> we need a ResourceProvider implementation as alternative, backed by all the existing functionality.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)