fix(test): make test_clean_requests_after_schema_grant more idempotent #19625
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Fix a potential table name conflict in integration tests
test_clean_requests_after_schema_grant
.Sometimes when the example database has
wb_health_population
's schema in another name---for example,public
instead ofNone
when in postgres (depending on how you configureSQLALCHEMY_EXAMPLES_URI
), rerunning this test will fail and report "table already exists" error from here. It seems the intention of the test was to reset table.schema to its original schema, but simply assumed it used to beNone
. This PR makes this test more idempotent by actually changing the schema of the same table to the original schema.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TESTING INSTRUCTIONS
Make sure CI passes.
ADDITIONAL INFORMATION