-
Notifications
You must be signed in to change notification settings - Fork 306
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
refactor: split system tests across modules #448
Conversation
This should make it easier to see which pandas tests we have and which we are missing.
To make this easier to review, I think I'll do this in multiple PRs. I don't want to accidentally miss a test. |
#475 should be merged before this. I'll probably split the "moves" into separate PRs as well (dbapi first, then pandas/arrow) |
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.
This looks a step in the right direction. We need to resolve a few the merge conflicts, though.
@tswast Or do you plan to abandon this and submit multiple smaller PRs instead?
I'll go with multiple PRs. (One for pandas and one for DB-API). I fear if I try to resolve merge conflicts, I'll accidentally delete some tests. |
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: - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/python-bigquery/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) Follow-up to #448 Towards #366
This should make it easier to see which pandas tests
we have and which we are missing.
Despite the branch name, not exactly related to #56, but I realized I was having trouble determining if this pandas DATETIME use case was tested when all system tests were in the same file.
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:
Towards #366