[Rd] Proposal: Mechanism for controlling the amount of testing 'R CMD check' performs

From: Henrik Bengtsson <hb_at_biostat.ucsf.edu>
Date: Sun, 08 Apr 2012 13:38:05 -0700


Hi,

I'd like to propose to introduce a standardized mechanism for controlling the amount of testing that 'R CMD check' performs together with an option to 'R CMD check' to specify if shallow or deep tests should be performed. I believe such a standardized feature would be useful, especially because the recent CRAN Policies needs to limit the computational load on CRAN servers, introducing an unfortunately conflict between writing writing thorough system tests and having light-weight tests for CRAN.

My solution to this has been to introduce use a system environment '_R_CHECK_FULL_', which I set to TRUE (or leave blank), and have my tests/*.R scripts test for this in order to either skip the test completely or do for instance down sample the data tested, e.g.

if (Sys.getenv("_R_CHECK_FULL_") != "TRUE") {   ...
}

Instead of such home-cooked solutions, I call for a more standardized mechanism, e.g.

if (tools::checkLoadOK("CRAN")) {
  ...
}

and

R CMD check --allowed-load=CRAN ...

where predefined levels could be NONE < MINOR < CRAN < DEFAULT < MAJOR < FULL, or similar.

This would also be useful in the iterative process of developing/testing new features of one's package.

Comments?

/Henrik



R-devel_at_r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel Received on Sun 08 Apr 2012 - 20:40:47 GMT

This quarter's messages: by month, or sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

All messages

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Tue 10 Apr 2012 - 16:30:44 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.

list of date sections of archive