Author: Shaun (flisakow@cs) Jan 9, 1995 I have finished re-organizing and re-working the test suites. I still need to work on adding samples to the new suites, but the programs themselves are done. To update to using the new test suite on your version of coral, do the following: cd $CORALROOT/src/coral /bin/rm -rf regression mkdir regression rcs_status -co -tree regression cd regression make setup The Test Suite is now divided into 5 suites: accept1: Primary Acceptance Tests accept2: Secondary Acceptance Test (These acceptance tests were there previously) C++_Interface: C++ Interface Tests server: Tests of Coral running in Server mode robust: Robustness Tests There is a program 'test_suite' at the top level which allows you to run any suite(s). ------------------- Usage: test_suite [options] [list of suites] Runs the specified test suites. If no list is provided, all available suites are run. Options: -h: Show usage (this message). -s: Show the available suites. -r: Produce a summary-type report only. -t : Specify timeout in minutes (per suite). -m : Mail output to user. Ex: test_suite -m coral@cs accept1 robust Ex: test_suite -r ------------------- A timeout for the suite and the ability to mail the output to a user have been added. (For multiple users, enclose all addresses in quotes "") Each suite has a directory by the same name and contains a program called 'run_suite' and a 'README' file explaining the tests there. The run_suite program has options similar to 'test_suite', but you may specify individual programs instead of suites. ------------------- Usage: run_suite [options] [list of programs] Runs the specified test programs in this suite. If no list is provided, all programs in the suite are run. Options: -h: Show usage (this message). -s: Show the programs available in this suite. -r: Produce a summary-type report only. -t : Specify timeout in minutes. -m : Mail output to user. Ex: run_suite -m coral@cs algebra1 ack Ex: run_suite -r ------------------- The 'server' suite is organized a little differently than the rest of the suites. Instead of "run" files in the 'run' directory. The server suite uses "play" files in the 'play' directory. These files contain commands to start a server, start clients, dump files into clients, verify output, etc. The "play" language these files are written in is discussed in detail in 'regression/server/play/README'. I have only written 1 simple script for the server suite so far, more need to be added. The 'robust' suite (which currently contains only 1 program) was added by me for the purposes of keeping track of bugs. Instead of just making an entry in some file when a program causes a core dump, the program can be added to this suite. That way, when someone wants to fix the bug, they will not need to search around or generate there own example of the necessary conditions for the error. If the programs are left in the directory after the problems have been fixed, they can also serve as guard against losing ground. Shaun