-
Notifications
You must be signed in to change notification settings - Fork 44
feat: Multi db test parametrization #436
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
feat: Multi db test parametrization #436
Conversation
The systems tests are failing because we don't have the Once the database created, populated with data, and indexes created, the tests should pass. |
Remove "database" argument from Query and AggregationQuery constructors. Use the "database" from the client instead. Once set in the client, the "database" will be used throughout and cannot be re-set. Parametrize the tests where-ever clients are used. Use the `system-tests-named-db` in the system test.
513e772
to
544dab7
Compare
This PR is now rebased against |
Systems test are now passing. |
I've updated these PRs and got the tests green. Seeking a go ahead for merging this. |
Removed a review request from Aza due to team transfer, but still seeking approval from a Python person. |
* feat: named database support (#398) * feat: Add named database support * test: Use named db in system tests * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md * Handle the case when client doesn't have database property * fix: add custom routing headers * Fixing tests for easier merge * fixing code coverage * addressing pr comments * feat: Multi db test parametrization (#436) * Feat: Parametrize the tests for multidb support Remove "database" argument from Query and AggregationQuery constructors. Use the "database" from the client instead. Once set in the client, the "database" will be used throughout and cannot be re-set. Parametrize the tests where-ever clients are used. Use the `system-tests-named-db` in the system test. * Add test case for when parent database name != child database name * Update owlbot, removing the named db parameter * Reverted test fixes * fixing tests * fix code coverage * pr suggestion * address pr comments --------- Co-authored-by: Vishwaraj Anand <[email protected]> --------- Co-authored-by: Bob "Wombat" Hogg <[email protected]> Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: Vishwaraj Anand <[email protected]> Co-authored-by: meredithslota <[email protected]>
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
This PR adds changes on top of #398, which was not yet merged to
main
.The changes are:
Client
, and the underlying queries and aggregation queries will retrieve thedatabase
id from theClient
.database_id
valuesdatabase_id
fieldFixes #<issue_number_goes_here> 🦕