'runtest' is the overall command which invokes the testing harness on a
given test suite. See 'runtest -h' or 'runtest --help' for a list of all
the options. Note that some options may not be currently functional. 
The option '-suite SUITE' is the only absolutely required option. Other
options, such as the compiler, are not needed if the compilerid field (for
this case) in the suite database table is set. And for this example if the
compilerid field is not set, then the "-compiler COMPILER" option will need
to be used on the runtest line. 

Make sure that the runtest command directory (found at <ROOT>/bin) is 
accessible within your path.

Here are the other values that are required in order to execute a test
using the runtest command:

   -host     * may be set on command line. If not it is picked up from
                   a gethostname() call for the current processor
   -user     * default found within config.xml file
   -compiler * default found within db table for a given suite
   -flag     * default found within db table for a given suite
   -makefile * default makefile name found within the config.xml file
   -homeqa   * default path found within the config.xml file

Some of the above values are to be found within the database tables. In 
particular:
   suite must be in the suite table
   host must be in the hosts table
   user must be in the users table
   compiler must be in the tools table
   flag must be in the flagdefs table and must correspond to the compiler
      tool via the validFlagdefCompilers table

See the documentation on database tables for more information.

How is a test actually run? See the documentation file test_info for
an example of using runtest to invoke a particular test or suite of tests.

Important information for some of the options to runtest:

-homeqa - where to find the test sources. This value is to the root directory
         which for the current implementation is <ROOT>/blackjack. Can be
         set on the command line to runtest if don't want to use the default
         value in the config.xml file.

-test - list particular tests (comma-separated) within a suite to run. The
    default behavior is to run all tests within a given suite.

-rmtest - list particular test (comma-sparated) within a suite not to run.
    The default behavior is to run all tests within a given suite.

-ctimeout - the compiler timeout value in seconds. The default can be set 
       within a test suite's database table, but if not set there and not 
       given on runtest line then internal default is 600 sec. Note that
       the timeout behavior of an individual test can be controlled by 
       setting the timeout column for that test within the suitetest
       database file. This timeout value is a multiplier for the ctimeout
       value.
       
-copysrc - copies the entire test source directory to the working directory.
       Especially useful when using the '-keep' option.

-etimeout - works just like ctimeout, but refers to the execution timeout.

-sim - a mechanism used to invoke the executables. Might be a general 
       command such as "time" (in fact, the prepopulated database has
       time as a simulator tool installed), or could be a simulator command
       or even a runner script which executes the program on a remote device.
