How the Test Scripts Work: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
mNo edit summary
Jadrian Miles (talk | contribs)
No edit summary
 
(4 intermediate revisions by one other user not shown)
Line 2: Line 2:


* Launch $G/src/gfxtest/gfxtest from a designated test machine.
* Launch $G/src/gfxtest/gfxtest from a designated test machine.
    Setup $G normally???
    Checkout src/gfxtest???


    src/gfxtest> ./gfxtest  [-noemail] [-notmp] [-d <result/]  mail,...
: Setup $G normally???
         -noemail - Do not email individual test reports to the recipients
: Checkout src/gfxtest???
                   in gfxtest.cfg.  By default failed tests mail a notification.
 
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.
                   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).
         -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
* gfxtest runs:  $G/src/gfxscripts/gfxtree-init
    A partial copy of $G is created locally in /ltmp.
 
    The files are extracted from cvs.
: A partial copy of $G is created locally in /ltmp.
    Separate duplicate copies are made for each supported architecture with:
: The files are extracted from cvs.
         src/gfxtest/   src/gfxscripts src/gfxtools-doc src/make
: Separate duplicate copies are made for each supported architecture with:
    A copy of $G/data/ is made for WIN32 and the Unix copies link to it.
 
         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.
* $G is set in gfxtest to the test copy.
    linux:  $G = /ltmp/gfxtest/gfx/tools/linux
: linux:  $G = /ltmp/gfxtest/gfx/tools/linux
    WIN32:  $G = /tmp/gfxtest/gfx/tools/WIN32
: WIN32:  $G = /tmp/gfxtest/gfx/tools/WIN32
 


* Tests are run on a test machines for each supported platform.
* Tests are run on a test machines for each supported platform.
  Currently these machines are:  ???
: Currently these machines are:  ???
 
 
* '''Script Files'''
: $G/src/gfxtest/gfxtest.cfg
:: A configuration file to designate individual tests to be run for each platform and subscribers to be notified when they fail.
 
: $G/src/gfxtest/gfxtest-project
:: Checkout, build, and install a project.  This is used to setup a test and is invoked via gfxtest/gfxtest.cfg.
 
: $G/src/gfxtest/gfxtest-nightly
:: Set up and run the tests via gfxtest/gfxtest.  Subscribers for test summaries are specified here.
 
: $G/src/gfxtest/gfxtest
:: Run tests that can be run on this platform and send notifications to subscribers.
 
: $G/src/gfxscripts/gfxtree-init
:: Create an initial $G framework in a temporary directory where tests are run.
 


* Script Files:
* '''Output Files Created When Tests are Run'''
: $G_TMP/gfxtest/gfxtest-summary.txt
:: A summary of test run results.


  $G/src/gfxtest/gfxtest.cfg
: $G_TMP/gfxtest/gfxtest-treeinit-output.txt
  $G/src/gfxtest/gfxtest
:: Output from creation of the $G tree.
  $G/src/gfxscripts/gfxtree-init


* Output Files created on each test machine:
: $G_TMP/gfxtest/gfxtest-<testcount>-<testName>-output.txt
:: Result output from an individual test.


  $G_TMP/gfxtest/gfxtest-summary.txt
[[Category:$G]][[Category:Software Development]]
  $G_TMP/gfxtest/gfxtest-treeinit-output.txt
  gfxtest-$testcount-$testName-output.txt

Latest revision as of 22:58, 6 March 2009

<<< 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
A configuration file to designate individual tests to be run for each platform and subscribers to be notified when they fail.
$G/src/gfxtest/gfxtest-project
Checkout, build, and install a project. This is used to setup a test and is invoked via gfxtest/gfxtest.cfg.
$G/src/gfxtest/gfxtest-nightly
Set up and run the tests via gfxtest/gfxtest. Subscribers for test summaries are specified here.
$G/src/gfxtest/gfxtest
Run tests that can be run on this platform and send notifications to subscribers.
$G/src/gfxscripts/gfxtree-init
Create an initial $G framework in a temporary directory where tests are run.


  • Output Files Created When Tests are Run
$G_TMP/gfxtest/gfxtest-summary.txt
A summary of test run results.
$G_TMP/gfxtest/gfxtest-treeinit-output.txt
Output from creation of the $G tree.
$G_TMP/gfxtest/gfxtest-<testcount>-<testName>-output.txt
Result output from an individual test.