From brian at braverock.com  Thu May 17 16:52:53 2012
From: brian at braverock.com (Brian G. Peterson)
Date: Thu, 17 May 2012 09:52:53 -0500
Subject: [Rd] test suites for packages
In-Reply-To: <4FB50C02.5050803@statistik.tu-dortmund.de>
References: <CAMi=pg6MRN9BxGQz4C=t6x=s1nGKGp_nLRyRwe6zSmKfs1_whA@mail.gmail.com>
	<4FB50C02.5050803@statistik.tu-dortmund.de>
Message-ID: <1337266373.18928.2.camel@brian-rcg>

On Thu, 2012-05-17 at 16:32 +0200, Uwe Ligges wrote:
> Yes: R CMD check does the trick. See Writing R Extension and read
> about a package's test directory. I prefer frameworks that do not
> obfuscate failing test results on the CRAN check farm (as most other
> frameworks I have seen).

Uwe:  I don't think that's completely fair.  RUnit and testthat tests
can be configured to be called from the R package tests directory, so
that they are run during R CMD check.

They don't *need* to be configured that way, so perhaps that's what
you're talking about.

-- 
Brian



[Rd] test suites for packages
Brian G. Peterson