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

refactor: split system tests across modules #448

Closed

Conversation

tswast
Copy link
Contributor

@tswast tswast commented Dec 22, 2020

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:

  • Make sure to open an issue as a bug/issue 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)

Towards #366

This should make it easier to see which pandas tests
we have and which we are missing.
@tswast tswast requested review from a team and stephaniewang526 and removed request for a team December 22, 2020 18:30
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Dec 22, 2020
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/python-bigquery API. label Dec 22, 2020
@tswast tswast requested review from plamut and removed request for stephaniewang526 January 7, 2021 15:34
@tswast tswast added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jan 19, 2021
@tswast
Copy link
Contributor Author

tswast commented Jan 19, 2021

To make this easier to review, I think I'll do this in multiple PRs. I don't want to accidentally miss a test.

@tswast
Copy link
Contributor Author

tswast commented Jan 19, 2021

#475 should be merged before this. I'll probably split the "moves" into separate PRs as well (dbapi first, then pandas/arrow)

Copy link
Contributor

@plamut plamut left a 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?

@tswast
Copy link
Contributor Author

tswast commented Mar 11, 2021

@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.

@tswast tswast closed this Mar 11, 2021
gcf-merge-on-green bot pushed a commit that referenced this pull request Mar 15, 2021
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. cla: yes This human has signed the Contributor License Agreement. do not merge Indicates a pull request not ready for merge, due to either quality or timing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants