[
https://issues.apache.org/jira/browse/SLING-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5508.
------------------------------------
Resolution: Fixed
Fixed in [r1729585|http://svn.apache.org/r1729585].
Also added some unit tests.
Internally some refactoring on the matchers was necessary to cover the
additional use cases.
[~rombert] Are you fine with those changes?
> Provide additional Hamcrest matchers
> ------------------------------------
>
> Key: SLING-5508
> URL: https://issues.apache.org/jira/browse/SLING-5508
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Apache Sling Testing Hamcrest 1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
>
> Currently the Hamcrest matchers provided in SLING-5063 only can match for
> some of the child names. An exact match is missing. Desired would be methods
> like
> # {{ResourceMatchers.containsChildren}}
> # {{ResourceMatchers.containsChildrenInAnyOrder}}
> similar to {{Matcher.contains}} and {{Matchers.containsInAnyOrder}}
> In addition it would be good to have a matcher on just a single resource for
> a given name like {{ResourceMatchers.resourceWithName}} and also a
> combination of the name matcher with the property matcher
> ({{ResourceMatchers.resourceWithNameAndProps}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
