-
Notifications
You must be signed in to change notification settings - Fork 883
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
[QST/Discussion] Reorganize pytests #4730
Comments
I think for cuIO the preferable path would be |
This issue has been labeled |
The plan for this will be discussed and decided upon in #11199 |
This PR adds documentation on how Python tests should be written. Related to #4730. This PR will establish best practices. Follow-up PRs will be needed to implement them. Resolves #6481. Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Bradley Dice (https://github.com/bdice) - Matthew Roeschke (https://github.com/mroeschke) - Lawrence Mitchell (https://github.com/wence-) - Ashwin Srinath (https://github.com/shwina) URL: #11199
Closing in favor of #15723, which is a bit updated and hopefully more discoverable. |
The pytests directory currently has a flat structure:
test/all_tests
.It might make sense to move tests to subfolders based on the operations/modules they might be most relevant to? Eg: All
IO
related tests can move toio/tests
like the pattern followed by dask or totests/io
like pandas.The text was updated successfully, but these errors were encountered: