On 12-03-03 03:56 AM, Mario Frasca wrote:
On Fri, 02 Mar 2012 12:15:48 -0500
pgilbert902 at gmail.com (Paul Gilbert) wrote:
Mario
[...] Examples only need to run, but in tests/ you can
do things like
if( 2*2 != 4 ) stop("arithmatic is messed up.")
problem is: when you do a stop, you stop
On Fri, 02 Mar 2012 12:15:48 -0500
pgilbert902 at gmail.com (Paul Gilbert) wrote:
> Mario
>
> [...] Examples only need to run, but in tests/ you can
> do things like
>
> if( 2*2 != 4 ) stop("arithmatic is messed up.")
>
problem is: when you do a stop, you stop, meaning you do not run
subsequen
Mario
I think of the RUnit and svUnit testing to be in addition to the
standard R package testing framework. You can get unit and more
integrated testing results, with the behaviour I think you are looking
for, simply by putting small test files in the tests/ directory of the
package. These
good day here,
I'm maintaining a couple of R modules, both on r-forge.
tests for these modules are written making use of unit testing, and I
make use of the svUnit module, part of SciViews-R.
I also make use of examples in the .Rd files.
my question regards 'R CMD check pkg'.
if an _example_ i
