[
https://issues.apache.org/jira/browse/SLING-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621443#action_12621443
]
Bertrand Delacretaz commented on SLING-475:
-------------------------------------------
Thinking about this again, it would be cool to be able to use the automated
tests as documentation of the sling:include details.
For example, a test could look like
uploadSlingIncludeScript("<sling:include resourceType='foo'>",
"/apps/include/include.jsp");
final String content = getContent(testNodeUrl);
assertContains(content, "main resource type == bar");
assertContains(content, "included resource type == foo");
For this to work, the uploadSlingIncludeScript method must be created to take a
skeleton test script, insert the sling:include statement in it and upload the
result.
The test scripts (main and included, maybe based on the same skeleton) would
just output lots of info like "main resource type == bar", "main selectors ==
a4 print", etc. that can be checked by the automated test code to verify the
results while documenting the behavior.
> Create Integration tests for the sling:include tag
> --------------------------------------------------
>
> Key: SLING-475
> URL: https://issues.apache.org/jira/browse/SLING-475
> Project: Sling
> Issue Type: Sub-task
> Components: Scripting JSP
> Reporter: Felix Meschberger
> Attachments: PatchWithError.patch, SLING-475.patch, sling475.patch,
> sling475.patch, sling475.patch, Sling475_simple_patch.patch, working.patch
>
>
> Summary says it all ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
