Trust is earned not
inherited importedFrom. Now that you’ve built a
cool package, you want potential users to trust it so that they might
adopt it. How to build trust in your piece of software? Unit testing is
part of the components building trustworthiness of your package. Imagine
you’re at the point where you’ve tested most lines of your code with
thorough assertions, including checks of edge cases. Proof of that hard
work will be a high test coverage, that potential users of your package
might notice thanks to a bright green coverage badge. But how would they
know your tests are thorough? That’s what
covrpage helps you with, by
creating a summary report of your tests that goes
beyond the coverage percentage. This way, potential users can see at a
glance how good the unit testing of your package is.
covrpage report only for users?
No, it can also inform your work on your package, by helping you track progress of the unit tests you’re working on, and it can show to potential contributors where help is needed.
# install.packages('remotes') remotes::install_github('yonicd/covrpage')
# assuming you are in your package root directory covrpage::covrpage() # create the covrpage and send directly to remote repository covrpage::covrpage(auto_push = TRUE) # Copy output as a vignette to use in pkgdown covrpage::covrpage(vignette = TRUE) # assuming you are not in your package directory covrpage::covrpage(path = 'another_directory')
covrpage can be outputed as a vignette called
Tests and Coverage
making it part of the package help documentation and can be viewed as an
in a pkgdown site.
Repositories using covrpage
If you also have
covrpage on your site and want to add it to the list
you can submit a Pull
to this README.
Locke Data contributed code and creative input into this package as part of their ongoing support offer designed to help boost the R ecosystem and support open source contributors. All rights associated with the work are granted to the copyright holder of this package.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Any questions/comments are always welcome in the issues section.