testExec.sh, testScheme.sh
  scripts to run all the test cases in ~comp210/Project/Connect5/Tests/Win/*,
  compare them with *.out, and print any differences.
  The scripts take a list of "games" as arguments, where a "game" is
  either the pathname of an executable or scheme program, or it is
  just the user-id of a comp210 student who has their program in
  the expected place.

testResults.txt
  The output of running eight test cases on all submissions.
  Note that some people failed for trivial reasons -- they transposed
  row/column, or their scheme code returned a move rather than printed it.

snafus/*
  see snafus/Readme

roster-{all,turnedin,tourney}
  a list of user-id's in the class, who had a connect5 file in the
  with the right name, and who passed all the tests, respectively.

findNoEntries.*
  Stuff to let people know they didn't have a connect5 file
  in the expected directory.

turnin-verify.sh

tourFinals
  The results of the tournament
*.out
  partial tournament results; can be deleted in a couple weeks (96.apr.30)

Here's what i [ian] have already done on running test cases: see the file

  cd ~comp210/Projects/Connect5/Tourney
  more testResults.txt

I ran eight basic test cases on all students;
any discrepencies are printed; no info => passed the tests.
(They are listed by user-id.)
There are a few special notes in that file too.

If you want to add any new test cases, put them in
   ~comp210/Projects/Connect5/Tests/Wins/foo
and the desired output in foo.out.
If you want to re-run the test cases for one or more students,
there are scripts testExec.sh and testScheme.h; pass them "-h" or
see the Readme for details.  (This scripts in teh Tourney directory.)

Similarly if you want to pit one program against another,
run "match-text" or "match-gui"; pass it -h or see Readme for details.
(These scripts are in ~comp210/bin, presumably in your path.)


So in the tournament, all of the seven finalists were
executable files.  I'd be interested in the success rate of passing
the test cases (and getting a functioning program)
among Schemers vs C'ers.

ian