[
https://issues.apache.org/jira/browse/SLING-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947960#comment-13947960
]
Bertrand Delacretaz commented on SLING-3478:
--------------------------------------------
Hi, sorry I overlooked that you were looking at the newer testing/tools. If we
can move away from requiring base classes there as well that would be good -
while keeping backwards compatibility of course.
The story is that the bundles/commons/testing module was created early in the
Sling history, and it it is still used by the launchpad/integration-tests
module that tests Sling itself, we didn't want to adapt all those tests.
But we recommend that people use the more modern testing/tools, so unless your
multiple instances tests are meant to be used inside the Sling codebase it's
fine for you to work in there. We should merge both approaches eventually, but
that's not planned right now.
> Facilitate writing of integration tests for multiple instances
> --------------------------------------------------------------
>
> Key: SLING-3478
> URL: https://issues.apache.org/jira/browse/SLING-3478
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Marius Petria
> Attachments: SLING-3478.patch
>
>
> Facilitate writing of integration tests for multiple instances. This is
> needed for better testing features like replication or topology discovery.
> Create a base class for such tests and a way to configure multiple instances
> and also sample integration test.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
