Run a Test: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<<< These are preliminary notes and may not be accurate. >>> | <<< These are preliminary notes and may not be accurate. >>> | ||
# [[How the Test Scripts Work]]. | |||
* Launch $G/src/gfxtest/gfxtest from a designated test machine. | * Launch $G/src/gfxtest/gfxtest from a designated test machine. | ||
| Line 37: | Line 39: | ||
$G_TMP/gfxtest/gfxtest-treeinit-output.txt | $G_TMP/gfxtest/gfxtest-treeinit-output.txt | ||
gfxtest-$testcount-$testName-output.txt | gfxtest-$testcount-$testName-output.txt | ||
# [[Subscribe to Test Results]] | |||
Tests are run daily and mail is sent when an individual tests fail. | |||
A summary of each test run is sent as well. | |||
* Subscribe to failure notifications for an individual test: | |||
Checkout and carefully edit: src/gfxtest/gfxtest.cfg | |||
Each line specifies a test to be run and contains: | |||
<testname> <testowners> <testarchs> <testcommand> <testcommandarg1> <..>; ... | |||
<testname> is a directory in $G/src/ | |||
<testowners> mail recipient | |||
<testarchs> {linux | WIN32 | OSX | sol | sgi},... | |||
<testcommand> Commands to run a test separated by a semicolon. | |||
usually: $G/bin/gfxtest-project <projectname> | |||
Blank lines are permitted. There is no provision for comment lines. | |||
* Subscribe to receive test summaries. | |||
To be filled in. | |||
# [[Run the Project Tests Locally]] | |||
To be filled in. | |||
[[Category:HOWTO]][[Category:$G]][[Category:Software Development]] | [[Category:HOWTO]][[Category:$G]][[Category:Software Development]] | ||
Revision as of 18:28, 8 January 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 $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
Tests are run daily and mail is sent when an individual tests fail. A summary of each test run is sent as well.
- Subscribe to failure notifications for an individual test:
Checkout and carefully edit: src/gfxtest/gfxtest.cfg Each line specifies a test to be run and contains:
<testname> <testowners> <testarchs> <testcommand> <testcommandarg1> <..>; ...
<testname> is a directory in $G/src/
<testowners> mail recipient
<testarchs> {linux | WIN32 | OSX | sol | sgi},...
<testcommand> Commands to run a test separated by a semicolon.
usually: $G/bin/gfxtest-project <projectname>
Blank lines are permitted. There is no provision for comment lines.
- Subscribe to receive test summaries.
To be filled in.
To be filled in.