Hi Betrand, 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. According to the source I cannot avoid the start of this server-process and thus I would need to configure it and make it work to avoid any test failures.
Is there any possibility to avoid the creation of this server-process and use an already running process? Thanks, Jörg 2014/1/13 Bertrand Delacretaz <bdelacre...@apache.org> > Hi Joerg, > > On Mon, Jan 13, 2014 at 2:44 PM, Jörg Hoh <jhoh...@googlemail.com> wrote: > > ...Taking [0] as example I feel a bit strange about the > getJunitServletUrl() > > method of the SlingRemoteTestParameters interface. It expects me to > return > > a URL where the serverside tests reside.. > > ...I would prefer if I could inject this parameter via maven, as I > already > > have a number of profiles available to separate these settings... > > The only real requirement for SlingRemoteTestRunner is that your test > implements SlingRemoteTestParameters, so you can very well supply the > base URL of the server under test via system properties or another > environment mechanism, won't that work for you? > > > ...In the end I would prefer to have a maven plugin where I can specify > these > > settings and which then connects to the server and fetches the > results.... > > Not sure if you need a specific plugin for that, my intention when > writing SlingRemoteTestRunner is that everything runs with the > standard Maven surefire or failsafe plugins, and you get results that > are as similar as possible to tests that run locally. If you have use > cases that aren't covered by that I'm happy to discuss them, but as is > I think you can specify the server URL via these plugins' system > properties options. > > -Bertrand > -- Cheers, Jörg Hoh, http://cqdump.wordpress.com Twitter: @joerghoh