How the Test Scripts Work

<<< These are preliminary notes and may not be accurate. >>>

• Launch $G/src/gfxtest/gfxtest from a designated test machine.

    Setup $G normally???
    Checkout src/gfxtest???

    src/gfxtest> ./gfxtest  [-noemail] [-notmp] [-d <result/]  mail,...
       -noemail - Do not email individual test reports to the recipients
                  in gfxtest.cfg.  By default failed tests mail a notification.
                  Successful test runs never cause mail to be sent.
       -notmp   - Run tests in the current $G tree.  Administrative use only.
       -d       - Store output files here (default is $G_TMP/gfxtest).

• gfxtest runs: $G/src/gfxscripts/gfxtree-init

    A partial copy of $G is created locally in /ltmp.
    The files are extracted from cvs.
    Separate duplicate copies are made for each supported architecture with:
       src/gfxtest/   src/gfxscripts  src/gfxtools-doc  src/make
    A copy of $G/data/ is made for WIN32 and the Unix copies link to it.
    

• $G is set in gfxtest to the test copy.

    linux:  $G = /ltmp/gfxtest/gfx/tools/linux
    WIN32:  $G = /tmp/gfxtest/gfx/tools/WIN32

• Tests are run on a test machines for each supported platform.

 Currently these machines are:  ???

• Script Files:

 $G/src/gfxtest/gfxtest.cfg
 $G/src/gfxtest/gfxtest
 $G/src/gfxscripts/gfxtree-init

• Output Files created on each test machine:

 $G_TMP/gfxtest/gfxtest-summary.txt
 $G_TMP/gfxtest/gfxtest-treeinit-output.txt
 gfxtest-$testcount-$testName-output.txt