-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
TST: Fix indexes test inheritance / fixturization #23825
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: Fix indexes test inheritance / fixturization #23825
Conversation
Hello @TomAugspurger! Thanks for submitting the PR.
|
Codecov Report
@@ Coverage Diff @@
## master #23825 +/- ##
==========================================
- Coverage 92.29% 92.29% -0.01%
==========================================
Files 161 161
Lines 51493 51490 -3
==========================================
- Hits 47524 47521 -3
Misses 3969 3969
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.
A couple comments not explicitly related to the diff, but in the spirit of the issue being resolved:
I think test_unique_na
can be moved from common.py
to test_base.py
: this test doesn't look to be taking advantage of inheritance at all, and appears to be exactly the same each time it's run by child classes inheriting from Base
.
Both test_has_duplicates
and test_duplicated
in common.py
are still using the indices
fixture. It doesn't look like they're causing an excess number of tests to be fully run, as these tests have a pytest.skip
baked in to skip cases when indices
doesn't match the type of index in the child class. This would be causing an excess of tests being skipped though, and is kind of a gross pattern. Would be fine leaving this as a follow up if that'd be preferred; seems like cleaning up these two tests could be in "good first issue" territory (or maybe a "good second issue" due to some complexity being present).
done.
hmm yes. As soon as I saw them using
|
yeah this is ok. we need to finish moving to all fixtures from the inhertence setup of the original (might even be an open issue about this). |
thanks |
Closes #23746
Before:
After: