-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Feature/scheduler/extend tests coverage #12114
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
base: main
Are you sure you want to change the base?
Feature/scheduler/extend tests coverage #12114
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 48s ⏱️ - 1h 43m 2s For more details on these failures, see this check. Results for commit c3d3dd1. ± Comparison against base commit 6004587. This pull request removes 4930 and adds 97 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
108ac09 to
ad50d37
Compare
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 9m 5s ⏱️ For more details on these failures, see this check. Results for commit c3d3dd1. ♻️ This comment has been updated with latest results. |
bentsku
left a comment
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.
Seems like lots of tests are still failing, might be worth putting the PR back in draft 😄 only had a comment unrelated to the failures that can already be addressed
| ) | ||
|
|
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.
nit: I'm not sure we need to snapshot this call, only snapshotting one create_schedule call in a non parametrized test should be enough. Here, we are recording 32 calls that are identical
Motivation
A user reported a regression for
get_scheduleerror code if the schedule was not found. To better understand this and also other discovered regressions and response errors from MOTO (used for implementing event bridge scheduler. And as a preparation for implementing a native localstack event bridge scheduler this PR adds AWS snapshot tests for the CRUD functionality of event bridge scheduler (https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/scheduler.html)The regressions are fixed in moto is this PR: getmoto/moto#8478
Changes
Add AWS snapshot tests for CRUD for schedules and schedule groups