-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: implement test_first #32274
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: implement test_first #32274
Conversation
@jbrockmendel I would love to open a PR parameterising these tests. Choosing a naming convention seems too difficult for me, tbh |
@@ -0,0 +1,61 @@ | |||
""" | |||
Note: includes tests for `last` |
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.
Could we just rename the file test_first_and_last.py
?
@@ -0,0 +1,69 @@ | |||
""" |
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.
Could we just rename the file test_first_and_last.py
?
Thanks @jbrockmendel I think naming the module test_first as you originally did is more consistent. Maybe we could have a test_last.py file which is just a comment that directs the contributor/reader to test_first.py |
cc @MomIsBestFriend there are three things about these tests that I think would make for good (separate) follow-ups if you're interested: