-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
APIGW: add negative tests for IntegrationResponse and improve error handling in PutIntegrationResponse and GetIntegrationResponse #12773
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: master
Are you sure you want to change the base?
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 20m 6s ⏱️ - 1h 23m 30s For more details on these failures, see this check. Results for commit e19873b. ± Comparison against base commit 99cd6da. This pull request removes 3748 and adds 5 tests. Note that renamed tests count towards both.
This pull request removes 712 skipped tests and adds 1 skipped test. Note that renamed tests count towards both.
|
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 37m 4s ⏱️ For more details on these failures, see this check. Results for commit e19873b. |
Test Results - Alternative Providers987 tests 589 ✅ 30m 28s ⏱️ Results for commit e19873b. |
Motivation
Add negative test coverage for the
IntegrationResponse
operation in API Gateway v1, to ensure LocalStack properly mimics AWS behavior when invalid inputs are provided. This improves parity and robustness of the emulated service.Changes
Added negative test coverage for
PutIntegrationResponse
andGetIntegrationResponse
operations:test_integration_response_wrong_api
test_integration_response_wrong_resource
test_integration_response_wrong_method
test_integration_response_wrong_invalid_statuscode
test_integration_response_invalid_responsetemplates
(skipped for now due to LocalStack/AWS parity gap)Updated
put_integration_response
andget_integration_response
inprovider.py
to:statusCode
using regex ([1-5]\d\d
)ValidationException
for invalid valuesNotFoundException
messages for missing resources, methods, or integration responsesTODO
What's left to do:
responseTemplates
input_integration_response
to ensure LocalStack raises appropriate exceptions (e.g.,SerializationException
,BadRequestException
) when invalid values are providedtest_integration_response_invalid_responsetemplates
once LocalStack behavior matches AWS