The default location for the binaries and scripts used for testing is the $TURBODIR directory. If you like to test some other, e.g., your local version of the TURBOMOLE binaries or scripts, you can specify the loading paths by the -l or -ls options for the binaries and scripts, respectively,
TTEST -l /usr/local/TURBOMOLE/bin/i786-pc-linux-gnu \ -ls /usr/local/TURBOMOLE/scripts.
TTEST -x /usr/local/TURBOMOLE/bin/i786-pc-linux-gnu/dscf.
If a test output is already present, e.g., in the TESTDIR directory, you may wish to check the results. This is accomplished by calling TTEST in check mode,
TTEST --check TESTDIR,
Testing parts of the TURBOTEST directory structure or the entire test suite at once is performed by calling the TTEST script from the appropriate place. The test script works recursively, executing all test examples underneath its starting directory. This requires that the test examples be arranged in a TURBOTEST-like directory structure,
progname/short|long/example (e.g., dscf/short/H2O.SCF.E1),
|TTEST dscf||called in the TURBOTEST directory, performs only the tests for DSCF module.|
|TTEST||called in the TURBOTEST/dscf directory, does the same.|
|TTEST -long||executes long examples for all modules.|
|TTEST ridft -short||performs all short examples from the ridft directory.|
Recursive testing creates some additional files in the central TURBOTEST directory. The global protocol file TESTPROTOKOLL.sysname contains short result messages for all test and a list of errors occurred. The list of failed tests is also written to the PROBLEMS.sysname file and can be rerun by calling the test script with the -r option,
TTEST -r PROBLEMS.i786-pc-linux-gnu.
Once you are done with testing, you may wish to clean up afterwards. To do it, use the -clean and -realclean options of the TTEST script. The difference between these two is that TTEST -clean deletes only the test directories and protocols that were created for the current computer architecture as returned by Sysname. In contrast, the TTEST -realclean wipes out all test directories and protocols that get in its way.