On Wed, 11 Jun 2008, Prof Brian Ripley wrote:
> Bill Dunlap wrote:
> > It might be nice if check could print the time it took to do
> > each test.
>
> That's an existing request for various parts of the checking procedure.
> When the time to run a package check jumps up, it is sometimes tedious to
On Wed, 11 Jun 2008, Bill Dunlap wrote:
On Wed, 11 Jun 2008, Kevin R. Coombes wrote:
[1] Because of the need for a nightly build of BioConductor, the tests
(in the ./tests directory) of a package that run routinely as part of "R
CMD check" must complete in five minutes.
[2] Nontrivial regressi
On Wed, 11 Jun 2008, Kevin R. Coombes wrote:
> [1] Because of the need for a nightly build of BioConductor, the tests
> (in the ./tests directory) of a package that run routinely as part of "R
> CMD check" must complete in five minutes.
> [2] Nontrivial regression testing of complex algorithms on
A combination of RUnit from CRAN and .Rbuildignore provide a workable
solution for the 'xts' package I work on, though this obviously
removes the tests from the distributed code.
http://cran.r-project.org/web/packages/RUnit/index.html
--and--
http://wiki.r-project.org/rwiki/doku.php?id=developer
