-
Notifications
You must be signed in to change notification settings - Fork 153
Maintenance: write end-to-end tests for the utility #1098
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
Comments
Waiting for the implementation to be completed first. |
After discussing, it seems that after merging #1416 it would be a good time to start working on the integration tests for Idempotency. As discussed, while testing, please also check whether the following issues can be closed or not; if not please consider commenting under them to report the missing delta:
Also, consider checking if it makes sense to move to |
|
Description of the feature request
Problem statement
Before a Powertools utility can be considered production ready it needs to have e2e tests implemented and running every time a new feature or release is added.
Summary of the feature
This action item tracks the activities and changes needed to integrate the new utility in the e2e tests, which high level and at the time of writing consist of:
Code examples
N/A
Benefits for you and the wider AWS community
Confidence that the utility has been tested in a real AWS Lambda execution environment.
Describe alternatives you've considered
N/A
Additional context
All utilities have extensive end to end test cases that aim at testing the different features and usages in a real AWS environment with real resources, permissions, and runtimes.
Related issues, RFCs
#447
The text was updated successfully, but these errors were encountered: