Skip to content
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

Fix protocol test issues #692

Merged
merged 1 commit into from
Jan 29, 2021
Merged

Fix protocol test issues #692

merged 1 commit into from
Jan 29, 2021

Conversation

mtdowling
Copy link
Member

Closes #686

Issue #, if available: 686

Description of changes:

This commit fixes various issues raised in #686. Some of this is related to just broken test cases (typically describing responses), and some of it is related to needing to indicate that a test case is meant to provide a client with an invalid response to ensure the client can gracefully handle it.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This commit fixes various protocol test issues for AWS JSON 1.0, 1.1,
and AWS REST JSON. In particular, this PR focuses on how request and
response payloads are formed when there is no defined input, no defined
output, an empty input, and an empty output. Various test cases have
been added that are tagged as either client-only or server-only to
ensure that both implementations are able to gracefully handle
different cases like en empty JSON object sent as the payload, or
omitting a payload altogether.

These test cases are based on actual observed behavior of AWS services
today. If we make changes to these protocols in the future, then we'll
update the protocol tests to reflect them (e.g., maybe we add support
for forcing an empty JSON object payload, omitting a payload, etc).

Closes #686
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarifying questions on the restJson1 protocol spec
4 participants