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 2014/10/13 17:41:33 UTC

[jira] [Updated] (SLING-4042) Testing: Donate sling-mock, jcr-mock, osgi-mock implementation

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

Stefan Seifert updated SLING-4042:
----------------------------------
    Fix Version/s: Testing Sling Mock Jackrabbit 1.0.0
                   Testing Sling Mock 1.0.0
                   Testing OSGi Mock 1.0.0
                   Testing JCR Mock 1.0.0

> Testing: Donate sling-mock, jcr-mock, osgi-mock implementation
> --------------------------------------------------------------
>
>                 Key: SLING-4042
>                 URL: https://issues.apache.org/jira/browse/SLING-4042
>             Project: Sling
>          Issue Type: New Feature
>          Components: Testing
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>             Fix For: Testing JCR Mock 1.0.0, Testing OSGi Mock 1.0.0, Testing Sling Mock 1.0.0, Testing Sling Mock Jackrabbit 1.0.0
>
>
> donate a at suite of mocking libraries to run OSGi/SCR, JCR and esp. Sling in a simulated "in-memory" environment for unit tests, ensuring minimal setup time. it uses either a mocked in-memory JCR, or the resourceresolver-mock implementation that is already part of the sling project. additional convenience features like bulk-loading JSON content and binaries into the simulated resource tree via a content loader makes it easy setting up complex text fixtures for your unit tests.



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