[
https://issues.apache.org/jira/browse/SLING-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-5356:
---------------------------------------
Description:
As discussed recently on our dev list the {{ContentBuilder}} currently provided
by the Sling Mocks library [1] can be very useful in testing. _(edit: while
implementing I have diverged from that idea and created a new, more powerful
{{ResourceBuilder}} API, for now that {{ContentBuilder}} stays unchanged)_.
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
was:
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
> New ResourceBuilder module - fluent API to create content structures
> --------------------------------------------------------------------
>
> 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.
> _(edit: while implementing I have diverged from that idea and created a new,
> more powerful {{ResourceBuilder}} API, for now that {{ContentBuilder}} stays
> unchanged)_.
> 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)
