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
Hi Jörg,
On Tue, Jan 14, 2014 at 10:13 AM, Jörg Hoh jhoh...@googlemail.com 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
Hi Bertrand,
yes, the initialisation of the JarExecutor fails. But I figured out howto
workaround it. You need to provide these statements as configuration to
your maven-failsafe-plugin:
systemPropertyVariables
test.server.urlhttp://localhost:8080/test.server.url
Hi Jörg,
I've created a maven plugin [1] and some common test classes [2]
specifically to make this easier for CQ5. The Granite IT maven plugin is
designed to work with the maven-failsafe-plugin by provided the readiness
check functionality and by exporting HTTP configuration properties using
the
Hi,
I am just exploring the possibilties to integrate my server side tests into
the maven build. I am already using the serverside JUnit tests mechanism
provided by Sling and I am quite happy with it. But the way how these tests
are currently integrated into the maven build process looks a bit
