Allow for continuous publishing of messages to RabbitMQ test queue in selected intervals#226
Merged
zroubalik merged 1 commit intokedacore:mainfrom Sep 18, 2025
Conversation
Signed-off-by: Wojciech Moczulski <wojciech.moczulski@stormlabs.eu>
7 tasks
zroubalik
approved these changes
Sep 17, 2025
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the RabbitMQ test utility to support continuous message publishing at specified intervals, enabling simulation of constant message flow for E2E testing of advanced RabbitMQ scaler trigger modes.
- Adds support for continuous message publishing with configurable intervals
- Maintains backward compatibility with existing single-batch publishing behavior
- Introduces interval-based loop control for sustained message generation
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
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
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.
By default
sendcommand ends its job after sending specified number of messages on to the RabbitMQ test queue. This change allows to repeatedly send number of messages in given interval (in seconds), allowing to simulate constant messages publication. It is necessary for E2E tests that validateDeliverGetRate,PublishedToDeliveredRatioandExpectedQueueConsumptionTimetrigger modes in RabbitMQ scaler.To use this feature, complete list of arguments must be provided to
sendcommand, where the fourth one represents interval value. No value for interval implies default operation model (send and quit).Checklist
References: