-
Notifications
You must be signed in to change notification settings - Fork 758
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
[feature request] a new exclude
argument into run_examples()
#2553
Comments
I'm not working on devtools at the moment, but made a quick visit while clearing notifications. One high-level observation I have about this issue and #2545 is that it feels like the participants are sort of approaching examples as if they are tests. The tidyverse team maintains a lot (>200) packages and I'm pretty sure none of us make regular usage of A lot of the features being requested are available already in the testing side of things and it just feels like the code where you need all of that control sounds more like test code than example code. |
@jennybc I have found that I use Having said that, I do think |
Is your feature request related to a problem? Please describe.
I am thinking about testing examples outside of R CMD CHECK. This would allow me specify more strict options like warning on partial argument match, lifecycle warnings to errors, even all warnings to errors and things like that. I could also try to use mocking in donttest and dontrun ones. These are just ideas right now that needs further refinement.
Describe the solution you'd like
Very likely I would encounter exceptions down the way so I would like to be able to exclude individual Rd files (or even individual examples if possible). Therefore I would need an
exclude
argument to therun_examples()
function. I feel it would give much better control than existingstart
argument.Describe alternatives you've considered
An alternative is to get .Rd files using non-exported devtools function, apply exclusions and then test individual examples using
pkgload::run_example()
.Additional context
Add any other context or about the feature request here.
The text was updated successfully, but these errors were encountered: