For ease of access the tester manual has been split into a number of sections:

• files Tester file definitions
• hints Tester usage hints
• language Tester language definition
• options Tester option descriptions
• sample Sample test specification
• workflow Tester work flow (running tests)

AVAILABILITY

DESCRIPTION

OPTIONS

• -all All, include blank lines in test
• -bench Print out a benchmark timing
• -class Give class of tests to include
• -delete Delete summary of results (TESTSPEC.result)
• -execute or -x; Execute shell and/or process
• -flow Show flow of test
• -generate Generate result files (SE,SO,SESO,...)
• -help Complete help screen
• -html Create html pages for tester
• -interactive Ask before executing a test
• -keep Keep all test files (not just failed output)
• -lines Show lines of test to standard error
• -man Create a man page for tester
• -nocleanup No clean up; don't execute after or afterall
• -other Other names to override local names
• -other @ Other names for additional names
• -process Process to read run command input
• -queuejobs Queue commands and execute shell or process
• -restart Restart for each test
• -shell Shell (sh,csh,ksh,tcsh with options)
• -tag Id to uniquely identify this run of tests
• -unclass Give class of tests to exclude
• -verbose Be verbose about it
• -without Do simple test ordering without the database
• -x or -execute; Execute shell and/or process
• -zipnames Zip names or names on non-word boundaries

Any number of files may be specified including wild carding

ENVIRONMENT

FILES

More on files

• files more info on tester files

SEE ALSO

BUGS

Names need separators to substitute. If you need ``front loaded'' names use the -zipnames option.

Process and shell commands that are not executable programs will only report that fact to the $FILESPEC .result file and tester will parse any requested test (no execution).

AUTHOR