From pgilbert902 at gmail.com  Wed Nov 26 21:08:50 2014
From: pgilbert902 at gmail.com (Paul Gilbert)
Date: Wed, 26 Nov 2014 15:08:50 -0500
Subject: [Rd] testing dontrun  examples
In-Reply-To: <54762580.50007@structuremonitoring.com>
References: <54761FC6.3090007@gmail.com>
	<54762580.50007@structuremonitoring.com>
Message-ID: <54763352.90303@gmail.com>

On 14-11-26 02:09 PM, Spencer Graves wrote:
> Hi, Paul:
>
>
>        "if(!fda::CRAN())" runs code except with "R CMD check ?as-cran".
> I use it so CRAN checks skip examples that (a) need the Internet or (b)
> take too long for CRAN.

Spencer

fda::CRAN() gives TRUE on my home machine, I think because I use several 
variables like  _R_CHECK_HAVE_MYSQL_=TRUE to control whether some tests 
get run. (Not all CRAN test servers have all resources.)

But, more importantly, wouldn't this strategy prevent CRAN from 
automatically running more extensive testing of the examples if they 
decided to do that sometimes?

Paul

>
>
>         Hope this helps.
>
>
>        Spencer
>
>
> On 11/26/2014 10:45 AM, Paul Gilbert wrote:
>> Is there a good strategy for testing examples which should not be run
>> by default? For instance, I have examples which get data from the
>> Internet. If I wrap them in try() then they can be skipped if the
>> Internet is not available, but may not be tested in cases when I would
>> like to know about the failure. (Not to mention that the example
>> syntax is ugly.)
>>
>> If I mark them \dontrun or \donttest then they are not tested. I could
>> mark them \dontrun and then use example() but for this, in addition to
>> run.dontrun=TRUE, I would need to specify all topics for a package,
>> and I don't see how to do this, missing topic does not work.
>>
>> Wishlist: what I would really like is R CMD check --run-dontrun pkg
>>
>> Suggestions?
>>
>> Thanks,
>> Paul
>>
>> ______________________________________________
>> R-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>
>



[Rd] testing dontrun examples
Paul Gilbert