R CMD check options for "more rigorous testing" - 2.15.0

Go To StackoverFlow.com


According to the release notes for 2.15:

There are new options for more rigorous testing by R CMD check selected by environment variables – see the ‘Writing R Extensions’ manual.

  1. Is "more rigorous" relative to the default set of checks?
  2. I can't find the supporting text in the manual. I'm sure I'm just missing it
  3. What options do I specify to perform the MOST rigorous testing?
2012-04-04 19:11
by SFun28


It seems that:

  1. YES, 'more rigorous' is relative to a default set of checks. The default checks do not test everything that can be tested.

  2. The most rigorous way to test is to specify all possible tests via config file values in check.Renviron (see R Internals and Writing R Plugins manuals)

  3. There is no easy way (i.e. command-line parameter) to check it all. A package author would have to maintain a config file (check.Renviron) as new versions of R are released.

2012-04-04 20:47
by SFun28
Points 2 and 3 are wrong. I never set env vars as you setting config file values is easier - Dirk Eddelbuettel 2012-04-04 20:55
good catch, updated my post. Is it accurate now - SFun28 2012-04-04 20:59


Try R CMD check --as-cran foo_1.2-3.tar.gz

The new --as-cran option gathers a few of these together; this was discussed on r-devel.

Also, a few weeks before R 2.15.0 came out, I added this to ~/.R/check.Renviron. These are documented in the 'R Internals' manual:

# See R Internals manual
2012-04-04 19:13
by Dirk Eddelbuettel
Thank you Dirk, this has just helped me. For people using devtools, use: check(args="--as-cran" - Tal Galili 2013-07-04 06:14
_R_CHECK_CRAN_INCOMING_=TRUE this explains why I didn't get spell check reports : - Gerhard Burger 2016-07-18 11:58