test :- add test for subscriber queue size behavior (Fixes #421) - #3299
Open
Aaravanand00 wants to merge 1 commit into
Open
Aaravanand00 wants to merge 1 commit into
Aaravanand00 wants to merge 1 commit into
Conversation
…2#421) Signed-off-by: Aaravanand <aaravanand@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a missing test in
test_subscription.cppto verify the behavior of a subscriber when its queue size (depth) is reached.It ensures that when a publisher rapidly publishes more messages than the subscriber's configured queue size (with
KEEP_LASThistory), the subscriber's RMW queue correctly behaves according to QoS settings and delivers only up todepthnumber of messages.Fixes #421
Is this user-facing behavior change?
No. This only adds a new test to the test suite to improve coverage.
Did you use Generative AI?
yes for testing the structure
Additional Information
The new test
queue_size_behaviorusestest_msgs::msg::BasicTypes. It sets up a subscriber with a queue depth of 3, waits for discovery, rapidly publishes 5 messages, and then spins to verify that the subscriber correctly receives exactly 3 messages without overflowing.