Torsten Hothorn wrote:
...
>> Browsing a bit in sources reveals that *.Rout.save is copy of R session
>> (starts with "welcome" text and later one code and output is there).
>> But how does one generate such a file?
>
> either R CMD BATCH or simply run R CMD check once and copy
> .Rcheck/tests/*.
On Mon, 24 Jul 2006, Gregor Gorjanc wrote:
> Martin Maechler stat.math.ethz.ch> writes:
>
>>
>>> "miguel" == miguel manese gmail.com>
>>> on Mon, 3 Jul 2006 09:43:12 +0800 writes:
>>
>> miguel> Hello, Do we have like an official unit testing
>> miguel> framework for packages
Martin Maechler stat.math.ethz.ch> writes:
>
> > "miguel" == miguel manese gmail.com>
> > on Mon, 3 Jul 2006 09:43:12 +0800 writes:
>
> miguel> Hello, Do we have like an official unit testing
> miguel> framework for packages? Like we do R CMD check, and
> miguel> say th
Thanks to both of you. I found it in some obscure paragraph (or maybe
I haven't read good enough, because after reading a couple of
paragraphs you'd think you got it already and skip the remaining) on
chapter 1, creating packages, about directory structure and on R CMD
check.
Cheers,
M. Manese
O
> "miguel" == miguel manese <[EMAIL PROTECTED]>
> on Mon, 3 Jul 2006 09:43:12 +0800 writes:
miguel> Hello, Do we have like an official unit testing
miguel> framework for packages? Like we do R CMD check, and
miguel> say the scripts in /test are executed?
yes. Just it's
miguel manese wrote:
> Hello,
>
> Do we have like an official unit testing framework for packages? Like
> we do R CMD check, and say the scripts in /test are executed?
The scripts are executed with R CMD check. What else do you need?
Uwe Ligges
> Or do we roll out our own outside the package?
>
Hello,
Do we have like an official unit testing framework for packages? Like
we do R CMD check, and say the scripts in /test are executed? Or
do we roll out our own outside the package?
Thanks,
M. Manese
__
R-devel@r-project.org mailing list
https://st
