-
-
Notifications
You must be signed in to change notification settings - Fork 284
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
Add section on testing R packages #1999
Conversation
@conda-forge/r feel free to adjust or make suggestions! |
@conda-forge/core ready for review |
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.
I think this is great advice. Especially when the test suite runs quickly, I think it makes sense to explicitly test the installed R package when building the recipe. Thanks @mfansler for writing up this documentation!
@conda-forge/core nudge |
@conda-forge/core bump |
Can you rebase this? Then we should be able to merge. |
For clarity, |
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Rebased; rendered preview LGTM. |
This fills out some guidance on testing R packages, with some specific directions on running
testthat
tests (a common testing framework).Note that one could have a simpler looking recipe by installing the tests (add
--install-tests
to build command) and test withtestthat::test_package('PackageName')
. However, I've omitted that since I believe it preferable to avoid delivering the test files to end users unnecessarily. Instead, I provide only the boilerplate that gives the same functionality sans copying. This is personally what I've shifted toward, but I still have some older recipes that install the tests.Happy to take suggestions!
PR Checklist: