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

add s3 protocol tests #2667

Merged
merged 2 commits into from
Jun 5, 2024
Merged

add s3 protocol tests #2667

merged 2 commits into from
Jun 5, 2024

Conversation

lucix-aws
Copy link
Contributor

Add smithy-borne s3-specific protocol tests. We have to do this manually for now because of our customization structure, see the comment.

@lucix-aws lucix-aws requested a review from a team as a code owner June 4, 2024 18:47
@lucix-aws lucix-aws force-pushed the feat-s3protocoltests branch from 8811a3e to 3b98cdf Compare June 4, 2024 18:50
Copy link
Contributor

@Madrigal Madrigal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do test GetBucketLocationUnwrappedOutput and S3OperationNoErrorWrappingResponse on the protocol test make sense for us?

t.Fatal("captured request is nil")
}

if tt.ExpectMethod != r.r.Method {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] can we assign a variable to r.r like req so we don't have to r.r our way on all tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do test GetBucketLocationUnwrappedOutput and S3OperationNoErrorWrappingResponse on the protocol test make sense for us?

yes, added them

can we assign a variable to r.r like req

done

@lucix-aws lucix-aws requested a review from Madrigal June 4, 2024 20:19
@lucix-aws lucix-aws merged commit 5b30240 into main Jun 5, 2024
12 of 13 checks passed
@lucix-aws lucix-aws deleted the feat-s3protocoltests branch June 5, 2024 13:51
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.

2 participants