Add developer docs for writing tests - #11199
Conversation
Codecov ReportBase: 87.47% // Head: 86.86% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## branch-22.12 #11199 +/- ##
================================================
- Coverage 87.47% 86.86% -0.61%
================================================
Files 133 135 +2
Lines 21826 21985 +159
================================================
+ Hits 19093 19098 +5
- Misses 2733 2887 +154
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This PR adds a primary developer guide for Python. It provides a more complete and informative landing page for new developers. When #11217, #11199, and #11122 are merged, they will all be linked from this page to provide a complete set of developer documentation. There is one main point of discussion that I would like reviewer comments on, and that is the section on directory and file organization. How do we want that aspect of cuDF to look? Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Matthew Roeschke (https://github.com/mroeschke) - Lawrence Mitchell (https://github.com/wence-) - Ashwin Srinath (https://github.com/shwina) URL: #11235
|
This PR has been labeled |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
wence-
left a comment
There was a problem hiding this comment.
Some minor comments, but overall looks good, thanks!
bdice
left a comment
There was a problem hiding this comment.
Minor changes suggested, otherwise LGTM.
|
rerun tests |
wence-
left a comment
There was a problem hiding this comment.
Very minor nit, but overall great! Thanks!
|
rerun tests |
shwina
left a comment
There was a problem hiding this comment.
LGTM w/ small suggestion/question.
|
rerun tests |
|
@gpucibot merge |
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.