-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Configured endpoint url resolver functional tests #2964
Configured endpoint url resolver functional tests #2964
Conversation
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## configured-endpoint-urls #2964 +/- ##
=========================================================
Coverage 93.32% 93.32%
=========================================================
Files 64 64
Lines 13662 13662
=========================================================
Hits 12750 12750
Misses 912 912 ☔ View full report in Codecov by Sentry. |
abfd5fa
to
b7c529a
Compare
6b8dba5
to
d4e3f56
Compare
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.
Looks like a good start. For this initial pass, I focused on seeing how we can trim the tests down to make it easier to walk through. In the next pass, we can focus more on the details on what cases we are testing
tests/functional/data/configured-endpoint-urls/test-cases/profile-tests.json
Outdated
Show resolved
Hide resolved
f93f7f9
to
966998f
Compare
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.
It's looking better. I just had some more comments related to cases we are testing and structuring the tests.
tests/functional/data/configured-endpoint-urls/test-cases/profile-tests.json
Outdated
Show resolved
Hide resolved
tests/functional/data/configured-endpoint-urls/test-cases/profile-tests.json
Outdated
Show resolved
Hide resolved
tests/functional/data/configured-endpoint-urls/test-cases/profile-tests.json
Outdated
Show resolved
Hide resolved
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.
Cool this looks good assuming CI passes. 🚢 Let's also make sure to squash this before merging it.
36a5f7a
to
60af11c
Compare
The tests use a data file to load tests that enumerate the ways that the endpoint URL can be defined and asserts that the correct endpoint is used in a request and that it is ignored correctly if the appropriate shared config file property or environment variable is supplied. They also assert that the correct config section name and environment variable name are used to configure and override the endpoint URL for every AWS service.
60af11c
to
d9a7dd9
Compare
Add functional testing for use of a configured endpoint url through the shared config file and environment variables.
First, the tests use a data file to load tests that enumerate the combinatorial ways that the endpoint URL can be defined (shared configuration file and environment variable for individual service and global/all services), and asserts that the correct endpoint is returned.
The tests also assert that the correct config section name and environment variable name are used to configure and override the endpoint URL for all services.
Lastly, the tests check that a operations for a subset of services use the endpoint override in a request.