Table of Contents

Name

testsuite -

Synopsis

testsuite [options] key=val

Description

testsuite runs a standard number of NEMO programs to excersize a core of frequently used NEMO programs.

Options

-b
force building new binaries for testsuite, and run the test
-c
clean the NEMO directory tree itself of Testfile in/out files by running
-f
force something
-h
help
-i
install something
-n
dry-run, only show which directories have Testfile’s
-q
query something
-r
cleanup and remove working directory $NEMO/tmp/testXXXXX afterwards
-s
show all the binaries that are needed for each test
-v
run all programs through valgrind. This will make the testsuite run very slowly, and it will be painfull to grep through the logfile.

Keywords

These are supplied after all options, and take the form KEYWORD=value. All keywords are in upper case, since they are ‘‘makefile’’ macros.
NBODY
Number of bodies. Should be at least 10 or so, making it less can break some code. Default: 10.
N
Size of a testimage. Default: 2.

Testfile

Each Testfile should have a standard number of targets:
help:        report the directory name
need:          report all NEMO binaries needed to run the test
all:           run all tests
clean:         clean up all data files created by "all"

Caveats

Listing a program in the BIN= macro of the Testsuite is sufficient to test a program when the testsuite is run with the -b flag, but not during a fresh install. For this it must also be added to the BINFILES= (or whichever appropriate) of the Makefile in order to be built.

See Also

mknemo(8NEMO) , need(8NEMO)

Author

Peter Teuben

Files


Testfile                            makefile with testsuite targets
$NEMO/src/scripts/testsuite            script
$NEMO/tmp/testXXXXX                   directory with data and log files

Update History


2-apr-97    V1.0: doc created           PJT
6-jul-01    documented newly added stuff    PJT
24-dec-04    added -v    PJT


Table of Contents