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
if you want to assert that X (x>1) messages are received in a kafka topic within XXXXXms, you will in most cases receive a false
Indeed, the "within" parameter will do a check every 100ms, so every 100ms it will poll messages, if one message is received, this "alone" message will be compared with a list (=> false) and immediately forget, then others polls will be done, each time comparing "alone" message with list and forget the "alone" message
The only case of success is if all message arrived in the same poll....
fix will consist in keeping in memory all the previous polled message, and compare the full list with the expected list
/!\ don't forget compliance with assertion on unique message , comparaison with "alone" message is ok
The text was updated successfully, but these errors were encountered:
Hello, we have to be very cautious about adding this type of behavior. Within guard at the moment are generic and it will not easy to add this behavior.
In the way of testing an app it can also add a lot of test instability to wait for this kind of assertion.
Maybe for your specific case, it can be better to add a steps assertion before X (x>1) messages are received in a kafka topic to be sure that all your kafka messages have been sent. (You can wait for specifics logs for example).
if you want to assert that X (x>1) messages are received in a kafka topic within XXXXXms, you will in most cases receive a false
Indeed, the "within" parameter will do a check every 100ms, so every 100ms it will poll messages, if one message is received, this "alone" message will be compared with a list (=> false) and immediately forget, then others polls will be done, each time comparing "alone" message with list and forget the "alone" message
The only case of success is if all message arrived in the same poll....
fix will consist in keeping in memory all the previous polled message, and compare the full list with the expected list
/!\ don't forget compliance with assertion on unique message , comparaison with "alone" message is ok
The text was updated successfully, but these errors were encountered: