You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending messages in an integration test it's pretty easy, due to lack of congestion on the queueing system, for example, to get messages in the originally expected order. It would be interesting to allow users to inject rules to screw up in some way message ordering.
This could be as easy as injecting into outgoing messages a do not deliver before header, even though it needs to be checked if it's supported on all transports.
Another option could be to inject a behavior in the incoming pipeline that simply delays message processing a bit or defers the incoming message and skips message processing.
The text was updated successfully, but these errors were encountered:
When sending messages in an integration test it's pretty easy, due to lack of congestion on the queueing system, for example, to get messages in the originally expected order. It would be interesting to allow users to inject rules to screw up in some way message ordering.
This could be as easy as injecting into outgoing messages a
do not deliver before
header, even though it needs to be checked if it's supported on all transports.Another option could be to inject a behavior in the incoming pipeline that simply delays message processing a bit or defers the incoming message and skips message processing.
The text was updated successfully, but these errors were encountered: