[
https://issues.apache.org/jira/browse/SLING-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301247#comment-14301247
]
Stefan Egli commented on SLING-4380:
------------------------------------
good point! I'll have a look at this at some point - currently I'd like to get
to a stable situation on jenkins first though (for discovery.impl that is) -
once that is confirmed I can look into this
> 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.0.14
>
>
> 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)
