From spencer.graves at pdf.com  Sat Jun  7 00:07:19 2008
From: spencer.graves at pdf.com (Spencer Graves)
Date: Fri, 06 Jun 2008 15:07:19 -0700
Subject: [Rd] Testing development code?
In-Reply-To: <alpine.LFD.1.10.0806062111430.16422@gannet.stats.ox.ac.uk>
References: <484992EA.2040401@pdf.com>
	<alpine.LFD.1.10.0806062111430.16422@gannet.stats.ox.ac.uk>
Message-ID: <4849B517.10008@pdf.com>

Dear Prof. Ripley: 

<in line>     

Prof Brian Ripley wrote:
> On Fri, 6 Jun 2008, Spencer Graves wrote:
>
>> Hi, R Core Team:
>>     How do you test the latest changes to the core R code?  Is it 
>> just "R CMD check"?  Or do you use other tools, like the perl "prove" 
>> module?
>>     I ask, because I'm about to start developing routine testing for 
>> other (non-R) software, for which I can't do "R CMD check", and I'd 
>> like to know what you do.
>
> 'make check-devel', 'make check-all' and regression tests of 
> (essentially) R CMD check over CRAN/BioC (the latter in arrears via 
> daily checking unless the change is thought likely to break things).
>
> If we were starting from scatch we would probably use a unit-testing 
> framework such as provided by Runits.
      How can I find information on 'Runits'?  Google led me to 
'http://en.wikipedia.org/wiki/Unit_test'.  The other hits I got did not 
seem as informative as Wikipedia. 

      Thanks for the reply.  This is helpful. 
      Spencer Graves
>
> C-based projects often use DejaGnu and similar -- scripting languages 
> usually use themselves to run their test suites.
>
>



[Rd] Testing development code?
Spencer Graves