-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Unskip fixed event filtering tests #11992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I'll create a PR shortly to fix the 2 use cases that are skipped now 👀 I didn't know about this, I would've tried to run them before! darn it 😄 |
Update regarding This is the rule: And this is the payload sent by ESM to the EventRuleEngine: {
"eventID": "455fabb3",
"eventName": "INSERT",
"dynamodb": {
"ApproximateCreationDateTime": 1733416705.0,
"Keys": {"id": {"S": "id_value"}},
"NewImage": {"id": {"S": "id_value"}},
"SequenceNumber": "49658361055172123998835686422808469640999919842681159682",
"SizeBytes": 23,
"StreamViewType": "NEW_AND_OLD_IMAGES"
}
} As you can see, the |
Update 2 regarding SQS: I'm unable to reproduce So I don't think there an issue per se with the current engine regarding ESM! I can see in the test another failure: EDIT: seems like EDIT2: seems like the issue stems from our handling of |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 30m 49s ⏱️ - 21m 58s Results for commit 5148fa0. ± Comparison against base commit 9f28c06. This pull request removes 958 and adds 13 tests. Note that renamed tests count towards both.
This pull request removes 97 skipped tests and adds 2 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Update on all issues:
All the other test failures seems to be related to the validation of the rule itself. Thanks again @joe4dev for raising this! |
Wow, amazing quick updates @bentsku 🙇 I fully agree with your conclusion:
|
1f5f2cc
to
0dfc89c
Compare
0dfc89c
to
766deaf
Compare
59c53d8
to
5148fa0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More test coverage is always good :D
Motivation
With @bentsku's new Python-based event filtering engine, we should be able to unskip tests that previously relied on the Java engine but were skipped to avoid JPype conflicts with StepFunctions JSONata.
Changes
TODO
numeric
operator string handling and provider validation for TestEventPattern #11994test_sqs_event_filter
to usepytest.param
(Example inaws.services.lambda_.event_source_mapping.test_lambda_integration_dynamodbstreams.TestDynamoDBEventSourceMapping.test_dynamodb_event_filter
) because it makes selective test execution and reporting so much easier and clearer.