moleculerjs / moleculer / 31790749002

94%

master: 94%

Pull #1367

github

test(e2e): wait for reverse registry sync before running scenarios

The supervisor's waitForNodes/waitForServices only guarantee that the
supervisor sees the remote nodes' services — not that the remote nodes
already know about the supervisor. With slow transporters (Kafka: INFO
propagation takes 1-1.5s through consumer fetch cycles) the remote node
silently drops events emitted towards the supervisor in that window,
which made the 'emit event' scenario flaky on Kafka + Local discoverer
(other discoverers are covered by the blanket 10s delay).

Wait until every remote node reports the supervisor as available in its
own registry before starting the scenarios.

Verified locally: 20/20 basic scenario runs with fresh topics on
Kafka+JSON+Local; the unfixed version failed on iteration 2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

5354 of 5913 branches covered (90.55%)

Branch coverage included in aggregate %.

7245 of 7481 relevant lines covered (96.85%)

517.86 hits per line