test: add e2e tests for batch processing #4978
Merged
+10,257
−14,067
Conversation
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
2 tasks
pull-request-size
bot
added
the
size/XL
boring-cyborg
bot
added
automation
Contributor
Author
|
Integration tests - including the new ones - are green. |
svozza
reviewed
Jan 29, 2026
dreamorosi
force-pushed
the
4489-maintenance-add-e2e-tests-for-batch-processing
branch
from
18a0bd0 to
267412c
Compare
Contributor
Author
|
Thanks for the review @svozza - good shouts on the simplification, I think I addressed most/all of them, let me know if this is what you had in mind. |
|
svozza
reviewed
Jan 29, 2026
Contributor
One tiny comment but other than that LGTM. |
svozza
approved these changes
Jan 29, 2026
dreamorosi
deleted the
4489-maintenance-add-e2e-tests-for-batch-processing
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Changes
This PR adds an integration test case for the Batch Processing utility, which was not previously covered. The test purposefully includes only one test case with standard SQS queue since the main goal of the test is to verify that the utility works in Lambda together with Parser, rather than covering the entire spectrum of features of the utility, which rely on similar implementations anyway.
To create this test I had to implement a new utility function that tails CloudWatch logs since this is also the first test that we add that can't be observed by querying logs or by collecting the response of a specific function invocation. This is due to the fact that we only publish messages to a SQS queue and we don't control how many or when the function invocations will happen.
This new testing utility lives under the packages/testing package and handles the tailing of a CloudWatch Log Group, collects the logs, and stops tailing after a given idle time.
Issue number: closes #4489
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.