In EventHub_MultipleDispatch_BatchSend, the test fail when the OperationId is compared. This only happens a single message is dispatched from Event Hubs v/s a batch of messages. It's non deterministic if Event Hubs will dispatch a single message or more than one message at a time as it might depend on timing in the backend. This explains why the failures are intermittent.
In EventHub_MultipleDispatch_IndependentMessages the test fails when the parent operation Id is expected to be null but is not.. In this case, there is no logic checking if one ore more than one messages were dispatched to the function handler and I believe the test fails when there is just one message as the Parent
The following two tests fail intermittently:
In EventHub_MultipleDispatch_BatchSend, the test fail when the OperationId is compared. This only happens a single message is dispatched from Event Hubs v/s a batch of messages. It's non deterministic if Event Hubs will dispatch a single message or more than one message at a time as it might depend on timing in the backend. This explains why the failures are intermittent.
In EventHub_MultipleDispatch_IndependentMessages the test fails when the parent operation Id is expected to be null but is not.. In this case, there is no logic checking if one ore more than one messages were dispatched to the function handler and I believe the test fails when there is just one message as the Parent