[
https://issues.apache.org/jira/browse/SLING-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998935#comment-12998935
]
Bertrand Delacretaz commented on SLING-1981:
--------------------------------------------
In revision 1074212, added a mechanism to run a single test method, example:
curl -X POST
http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.sampletests.JUnit4Test.json/testRequiresBefore
This is using the usual Sling convention, adding the test method name as a
suffix after the extension
> Create a sample that demonstrates our testing tools and techniques
> ------------------------------------------------------------------
>
> Key: SLING-1981
> URL: https://issues.apache.org/jira/browse/SLING-1981
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Labels: integration-tests, junit, testing
>
> Although our Launchpad tests can be used as examples of how to test Sling
> applications, we should create a much simpler sample project that
> demonstrates the following testing tools and techniques:
> 1) Start a Sling instance and wait for it to be ready
> 2) Run simple HTTP integration tests against that instance
> 3) Run server-side JUnit tests using @TestReference to access OSGi services
> (SLING-1963)
> 4) Run server-side scriptable tests (SLING-1963)
> The tests should run in the integration-tests phase of the Maven build.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
