-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
TST/REF: Add more pytest idiom to tests/tslib #24587
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
TST/REF: Add more pytest idiom to tests/tslib #24587
Conversation
fefffc1
to
16c4d84
Compare
Codecov Report
@@ Coverage Diff @@
## master #24587 +/- ##
==========================================
- Coverage 92.38% 92.38% -0.01%
==========================================
Files 166 166
Lines 52478 52478
==========================================
- Hits 48483 48482 -1
- Misses 3995 3996 +1
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24587 +/- ##
===========================================
- Coverage 92.36% 43.03% -49.33%
===========================================
Files 166 166
Lines 52497 52497
===========================================
- Hits 48489 22593 -25896
- Misses 4008 29904 +25896
Continue to review full report at Codecov.
|
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.
looks good. some comments.
Is this just getting rid of a level of indentation by removing the classes? I get that they don't serve much functional purpose, but do find them helpful for organization. Is there a preferred idiom for organization? |
@jbrockmendel : In general, small, modular, functional test cases would be preferred I think (both for consistency with pytest idiom and readability, especially the short and modular part). I agree that test classes can be useful, especially when we are sharing test cases amongst multiple files or the test file is massive and has several super distinct collections of tests. That being said, for this situation, I did not really find that to be the case for I don’t think we will have a unified style for tests. We might prefer functional, but I wouldn’t force it everywhere if the (semantic) organization does not dictate it to be so. |
16c4d84
to
646af2f
Compare
@jreback : Addressed all comments, and everything is green. PTAL. |
thanks @gfyoung |
I was planning to correct individual files, but then I began to realize that the fixes were involving more and more files (was shifting tests around) in the directory, to the point that I just modified them all. 🙂