[ 
https://issues.apache.org/jira/browse/SLING-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051158#comment-15051158
 ] 

Bertrand Delacretaz commented on SLING-5356:
--------------------------------------------

I have now added file support, here's a builder call that creates the tree of 
the second comment above.

{code}
        getBuilder(testRootPath)
            .resource("apps/myapp/components/resource")
            .siblingsMode()
            .file("models.js", getClass().getResourceAsStream("/models.js"), 
"MT1", 42)
            .file("text.html", getClass().getResourceAsStream("/text.html"), 
"MT2", 43)
            .resetParent()
            .hierarchyMode()
            .resource("apps")
            .file("myapp.json", getClass().getResourceAsStream("/myapp.json"), 
"MT3", 44)
            .resetParent()
            .resource("apps/content/myapp/resource")
            .resetParent()
            .resource("apps/content", "title", "foo")
            .file("myapp.json", getClass().getResourceAsStream("/myapp.json"), 
"MT4", 45)
            .commit()
            ;
{code}

> 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)

Reply via email to