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

Stefan Seifert updated SLING-3969:
----------------------------------
    Affects Version/s:     (was: Testing ResourceResolver Mock 0.2.0)
                       Commons Testing 2.0.16

Completed: At revision: 1627361  

documentation updated as well, please cross-check

bq. What about deprecating 
https://svn.eu.apache.org/repos/asf/sling/trunk/bundles/commons/testing/src/main/java/org/apache/sling/commons/testing/sling/MockResource.java
 as well?

not sure, this still may have use when you want to make a very simple unit test 
where you only need a single resource and not a complete resource resolver. 
although nowadays it should be easier to use Mockito mocking then, than this 
implementation. so i leave it un-deprecated for now, but perhaps others have 
opinions as well.

> Include a link to the new resourceresolver mock module
> ------------------------------------------------------
>
>                 Key: SLING-3969
>                 URL: https://issues.apache.org/jira/browse/SLING-3969
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Commons Testing 2.0.16
>            Reporter: Konrad Windszus
>            Assignee: Stefan Seifert
>            Priority: Trivial
>
> Can you please mention the new resourceresolver mock in 
> http://sling.apache.org/documentation/tutorials-how-tos/testing-sling-based-applications.html#mock-classes-and-services.
>  
> Also please deprecate the old one in 
> https://github.com/apache/sling/blob/trunk/bundles/commons/testing/src/main/java/org/apache/sling/commons/testing/sling/MockResourceResolver.java
>  in favour of 
> https://github.com/apache/sling/blob/trunk/testing/resourceresolver-mock/src/main/java/org/apache/sling/testing/resourceresolver/MockResourceResolver.java.
> The same applies to MockResourceResolverFactory and related classes.



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

Reply via email to