-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
TST: use fixtures for some sql database connections #42976
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
Conversation
This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. |
Thanks for the PR but appears that it has gone stale. Feel free to reopen if you have time to continue working on it! |
@@ -367,6 +375,270 @@ def test_frame3(): | |||
return DataFrame(data, columns=columns) | |||
|
|||
|
|||
@pytest.fixture |
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.
Does it makes sense for the the engine and connection fixtures to be scope="module"
so they are not repeatedly created and destroyed?
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.
The fixtures also do cleanups after each test. So it's better to have a new engine/conn for each test. Also, they don't seem to add much overhead.
@fangchenli happyt o take this if you can fixup |
thanks @fangchenli |
xref #40686
This PR:
We probably should put all the fixtures in a separate conftest.py file. But since there are unmerged PRs related to this test file, I kept everything in one place for now to avoid conflict.