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 2018/08/29 19:34:00 UTC

[jira] [Resolved] (SLING-7867) sling-mock: Dynamically resolve SlingBindings properties

     [ https://issues.apache.org/jira/browse/SLING-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert resolved SLING-7867.
-----------------------------------
    Resolution: Fixed

https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/0ce99a0ae836d1143ca1a07545649fc615854499

> sling-mock: Dynamically resolve SlingBindings properties
> --------------------------------------------------------
>
>                 Key: SLING-7867
>                 URL: https://issues.apache.org/jira/browse/SLING-7867
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Major
>              Labels: mocks
>             Fix For: Testing Sling Mock 2.3.4
>
>
> currently, the SlingBindings object is initialized statically when the mock context is created.
> but some properties - especially the current resource - may change during the testing code, but should nevertheless always point to the correct result.
> we should resolve the SlingBindings properties dynamically to the current mock context, and also allow this for subclasses of SlingContextImpl.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)