You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dirk Rudolph (JIRA)" <ji...@apache.org> on 2016/12/10 19:29:58 UTC

[jira] [Commented] (SLING-6388) Support tracking changes of JCR Mock MockSession

    [ https://issues.apache.org/jira/browse/SLING-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738353#comment-15738353 ] 

Dirk Rudolph commented on SLING-6388:
-------------------------------------

The Unit tests I wrote for SLING-6387 unfortunately fail as {{hasChanges}} doesn't return the expected value.

> Support tracking changes of JCR Mock MockSession
> ------------------------------------------------
>
>                 Key: SLING-6388
>                 URL: https://issues.apache.org/jira/browse/SLING-6388
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing JCR Mock 1.1.16
>            Reporter: Dirk Rudolph
>            Priority: Minor
>
> {{org.apache.sling.testing.mock.jcr.MockSession#hasPendingChanges}} always returns {{false}}. This causes the {{ResourceResolver}} to return {{false}} for {{hasChanges()}} as well, making it difficult to use the JCR Mock {{ResourceResolverType}} for tests of transactional implementations using {{ResourceResolver}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)