RStudio is becoming Posit in October. Learn more at posit.co
RStudio is becoming Posit in October.
Learn more at posit.co
The premier IDE for R
RStudio anywhere using a web browser
Put Shiny applications online
Shiny, R Markdown, Tidyverse and more
Next level training for you and your team
Do, share, teach and learn data science
An easy way to access R packages
Let us host your Shiny applications
A single home for R & Python Data Science Teams
Scale, develop, and collaborate across R & Python
Easily share your insights
Control and distribute packages
RStudio
RStudio Server
Shiny Server
R Packages
RStudio Academy
RStudio Cloud
RStudio Public Package Manager
shinyapps.io
RStudio Team
RStudio Workbench
RStudio Connect
RStudio Package Manager
Webinars RStudio Essentials
Measure and report test coverage for R, C, C++ and Fortran code in R packages
September 23, 2016
Code coverage records whether or not each line of code in a package is executed by the package’s tests. While it does not check whether a given program or test executes properly it does reveal areas of the code which are untested.
Coverage has a long history in the computer science community (Miller and Maloney in Communications of the ACM, 1963), unfortunately, the R language has lacked a comprehensive and easy to use code coverage tool. The covr package was written to make it simple to measure and report test coverage for R, C, C++ and Fortran code in R packages. It has measurably improved testing for numerous packages and also serves as an informative indicator of package reliability. Covr is now used routinely by over 1000 packages on CRAN, Bioconductor and GitHub. In this webinar we’ll discuss how covr works, how it is best used and how it has demonstrably improved test coverage in R packages since its release.
Jim is a software engineer on the Tidyverse team, with a background in Bioinformatics and Genomics. He is the author and maintainer of a number of R packages including covr, devtools, glue, readr and more…