Hi Jörg, On Tue, Jan 14, 2014 at 10:13 AM, Jörg Hoh <[email protected]> wrote: > ...I took your approach using SlingRemoteTestRunner and maven-failsafe-plugin, > and I got pretty far. The problem is now, that I SlingTestBase forks a new > server-process which runs the server-side tests. But on my side I have an > already running Sling instance (CQ) and I want to leverage this instance...
I agree that this should work, looking at [1] if you set launchpad.http.server.url that should prevent that class from starting its own instance, but maybe the JarExecutor setup fails if you do that? If that's correct we should fix that, you probably only need the server ready detection from SlingTestBase, so we might want to factor that out. I've been trying to avoid forcing such base class inheritance lately as that's not very convenient, we can probably improve that. -Bertrand [1] http://svn.apache.org/repos/asf/sling/trunk/testing/tools/src/main/java/org/apache/sling/testing/tools/sling/SlingTestBase.java
