i've used the teleporter rules in the integration tests for the context-aware 
configs:
https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/contextaware-config/integration-tests

on my machines they run smooth on a fast machine, but flaky on a not-so-fast 
machine.

source of the problem is that the integration tests sometimes start before the 
ResourceResolverFactory service becomes available, it's a racing condition.

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?

stefan

Reply via email to