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 Egli (JIRA)" <ji...@apache.org> on 2016/07/04 07:32:11 UTC

[jira] [Updated] (SLING-4380) Use sling mocks for the discovery impl tests

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

Stefan Egli updated SLING-4380:
-------------------------------
    Fix Version/s:     (was: Discovery Impl 1.2.8)
                   Discovery Impl 1.2.10

> Use sling mocks for the discovery impl tests
> --------------------------------------------
>
>                 Key: SLING-4380
>                 URL: https://issues.apache.org/jira/browse/SLING-4380
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions, Testing
>    Affects Versions: Discovery Impl 1.0.12
>            Reporter: Robert Munteanu
>             Fix For: Discovery Impl 1.2.10
>
>
> The org.apache.sling.discovery.impl has its own utility mocks in https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/discovery/impl/src/test/java/org/apache/sling/discovery/impl/setup/ . Most of these can be replaced by the new Sling mocks.
> The benefits would be:
> - less maintenance for the discovery impl project
> - more exposure/coverage for the Sling mocks



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