R test coverage
Hi Jim, Thanks for the info. I disregarded covr in my search results as I thought it would only apply to packages outside base and recommended. The code is pure R code so it might work, but it reads a file so it might involve some C code. Thanks! Llu?s
On Mon, 27 Nov 2023 at 20:11, Jim Hester <james.f.hester at gmail.com> wrote:
It should be possible to use covr to do this, see this old issue (https://github.com/r-lib/covr/issues/59). However interpreting the results can prove challenging as naturally covr uses functions from the base internally. Unfortunately the base and many of the internal and recommended packages have somewhat bespoke installation, so it would likely take some additional work on your end to get reporting working. I had thought of doing this at one point, but wasn't sure there would be any audience for the results, so did not pursue it further. For measuring coverage of the C code in the R runtime alone you could use gcov and run the test suite, which depending on your contribution may be the most informative route. (replying for the list, accidentally replied only to Llu?s the first time) On Mon, Nov 27, 2023 at 10:15?AM Llu?s Revilla <lluis.revilla at gmail.com> wrote:
Hi all, I recently proposed a change in R that has led to the addition of new
code
to the R source code. The code added, as far as I know, has no tests and it might affect many packages in CRAN. I was wondering if adding a test would be helpful or it is already
covered
by some other test.
Which brought me to the question: what is the coverage of R checks
(check-devel)?
My searches in the mailing list or other places didn't return anything
close to it.
But I am curious if someone has already done this and how.
Many thanks,
Llu?s
[[alternative HTML version deleted]]
______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel