You can clone with
Cannot retrieve contributors at this time
In this directory, various tests on R are run automatically.This is the recommended way to check if R has been built successfully onyour architecture. make test-Alldoes both of make test-Examplesand make test-Specificthe first of which runs all the examples from the help files (*.Rd) ofall core packages (base, eda, ..., ts) -- which can take quite long (afew minutes, depending on your environment).The "fast" part of the tests is `test-Specific' which runs the *.Rfiles in this (./tests) directory (tolerantly) compares the result*.Rout file with the prespecified *.Rout.save (if that exists). Italso runs a test abusing all the functions via no-segfault.R, and thatcan be quite slow (a minute or more).There are other useful make targets: make test-undoc make test-codocrun undoc() and codoc() on base and all the standard packages. make test-Regruns regression tests, that is tests that ensure that things which have beenchanged (perhaps as a result of bug reports) stay fixed. make test-Randomruns a series of tests on the distribution of random variates generatedby the rxxxx() functions. The test is a large deviation bound on the Kolmogorov statistic, so also provides a test of the cumulative distributionfunctions pxxxx(). Because rare events do happen, this test suitewill be failed in about 1 in 50 runs. make test-Internetruns tests which need access to the Internet and/or sockets and so maynot run on every machine. You will see some differences in the output,but no test should fail if you do have sockets and Internet access. make test-Gctruns a subset of the specific tests with gctorture turned on. This is slow,taking an hour or two.Martin Maechler for the R Core Team.