ah, thanks for the hint. works fine. created https://issues.apache.org/jira/browse/SLING-6031 for the final solution within the teleporter rule.
stefan >-----Original Message----- >From: Bertrand Delacretaz [mailto:[email protected]] >Sent: Friday, September 2, 2016 2:29 PM >To: dev >Subject: Re: flaky integration tests with teleporte rule > >Hi Stefan, > >On Fri, Sep 2, 2016 at 12:32 PM, Stefan Seifert <[email protected]> >wrote: >> >> ...in the old HttpTestBase there was a concept with launchpad.ready.1 >URLs defined which were checked to see if the >> instances was really ready - is there an equivalent concept in the >teleporter rule, how to configure it?... > >Ah, the "are we ready yet" topic ;-) > >In the repoinit tests I'm using a locally implemented WaitFor class >for that, we might want to move that to the teleporter client module, >and maybe implement a more declarative way of defining the required >services. But for now that should help you. > >-Bertrand > >[1] >https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/repoinit >/it/src/test/java/org/apache/sling/repoinit/it/WaitFor.java
