[
https://issues.apache.org/jira/browse/SLING-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5043.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1703762
(!) this has one drawback when testing with "real" repositories like
jackrabbit, oak: those repositories are not "cleared" after each test run, as
it is the case with jcr-mock, resourcersolver-mock. before it was possible to
do a unit test with and import and further tests without any "commit()" at all,
and there was no need for cleanup.
now it's required that at least imported content is removed in the unit test
again after the test run. still, the change makes sense.
> sling-mocks: Execute commit() after ContentLoader operations
> ------------------------------------------------------------
>
> Key: SLING-5043
> URL: https://issues.apache.org/jira/browse/SLING-5043
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock 1.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock 1.5.2
>
>
> as discussed in SLING-5028 after each ContentLoader import call a commit()
> should be executed. this is esp. important when "real" jackrabbit or oak
> repositories are used, and what users would expect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
