[
https://issues.apache.org/jira/browse/SLING-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048973#comment-15048973
]
Bertrand Delacretaz commented on SLING-5356:
--------------------------------------------
I have commited a first work-in-progress version at
http://svn.apache.org/r1718908.
For now the interesting bits are the ResourceBuilder interface, demonstrated by
the ResourceBuilderImplTest.
Building a small tree looks like this:
{code}
builder
.resource("a/b/c", "title", "foo", "count", 21)
.siblingsMode()
.resource("1")
.resource("2")
.resource("3")
.hierarchyMode()
.resource("with")
.resource("more/here", "it", "worked")
.resource("deepest", "it", "worked")
.commit();
{code}
As a next step I'm planning to add support for loading ContentLoader definition
files.
> Extract and generalize the Sling Mocks ContentBuilder
> -----------------------------------------------------
>
> Key: SLING-5356
> URL: https://issues.apache.org/jira/browse/SLING-5356
> Project: Sling
> Issue Type: New Feature
> Components: General
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> As discussed recently on our dev list the {{ContentBuilder}} currently
> provided by the Sling Mocks library [1] can be very useful in testing.
> In order to make it usable for both client-side and server-side testing (as
> well as in server-side code) I'm planning to
> * Extract it into its own module
> * Define an API that allows for creating nodes and properties, importing JSON
> and other files via the Sling ContentLoader and providing a simple a way to
> cleanup the test content
> * Implement (first) a server-side version of that API
> * Implement (as a second priority) a client-side version that can be used in
> test run via HTTP
> This shouldn't affect the existing Sling Mocks library users, except maybe
> forcing them to rebuild their tests to use the new API.
> [1]
> https://sling.apache.org/documentation/development/sling-mock.html#building-content
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
