Run a Test - Revision history

Jadrian Miles at 22:57, 6 March 2009

2009-03-06T22:57:36Z

← Older revision		Revision as of 22:57, 6 March 2009
Line 13:		Line 13:


	~~[[Category:HOWTO]]~~[[Category:$G]][[Category:Software Development]]		[[Category:$G HOWTO]][[Category:Software Development]]

Brad Berg at 13:29, 9 January 2009

2009-01-09T13:29:48Z

← Older revision		Revision as of 13:29, 9 January 2009
Line 1:		Line 1:
	<<< These are preliminary notes and may not be accurate. >>>		<<< These are preliminary notes and may not be accurate. >>>

			Programs should have a simple test to ensure the most basic functions are working. The test should run in a reasonable amount of time on par with the time it takes to build the program. These simple smoke tests need to be fully automated. Additional tests that are more comprehensive can also be provided, but need not be included as part of the automated test system.

	# [[How the Test Scripts Work]]		# [[How the Test Scripts Work]]

Brad Berg at 20:36, 8 January 2009

2009-01-08T20:36:56Z

← Older revision		Revision as of 20:36, 8 January 2009
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]].		# [[How the Test Scripts Work]]
			#: An overview of the test mechanism.
	# [[Subscribe to Test Results]]		# [[Subscribe to Test Results]]
			#: Receive summaries of daily test runs or notifications when specific tests fail.
	# [[Run the Project Tests Locally]]		# [[Run the Project Tests Locally]]
			#: Manually run tests or schedule them to be run automatically.
			# [[Add a Test to a Project]]
			#: Write tests for a project so they will work with the test driver.



	[[Category:HOWTO]][[Category:$G]][[Category:Software Development]]		[[Category:HOWTO]][[Category:$G]][[Category:Software Development]]

Brad Berg at 18:33, 8 January 2009

2009-01-08T18:33:50Z

← Older revision		Revision as of 18:33, 8 January 2009
Line 2:		Line 2:

	# [[How the Test Scripts Work]].		# [[How the Test Scripts Work]].

	# [[Subscribe to Test Results]]		# [[Subscribe to Test Results]]

	# [[Run the Project Tests Locally]]		# [[Run the Project Tests Locally]]

Brad Berg: Replacing page with '<<< These are preliminary notes and may not be accurate. >>> # How the Test Scripts Work. # Subscribe to Test Results # Run the Project Tests Locally [[Cat...'

2009-01-08T18:33:28Z

Replacing page with '<<< These are preliminary notes and may not be accurate. >>> # How the Test Scripts Work. # Subscribe to Test Results # Run the Project Tests Locally [[Cat...'

@@ Line 2: / Line 2: @@
 # [[How the Test Scripts Work]].
 # [[Subscribe to Test Results]]
-Tests are run daily and mail is sent when an individual tests fail.
+# [[Run the Project Tests Locally]]

Brad Berg at 18:28, 8 January 2009

2009-01-08T18:28:48Z

@@ Line 1: / Line 1: @@
 <<< These are preliminary notes and may not be accurate. >>>
 * Launch $G/src/gfxtest/gfxtest from a designated test machine.
@@ Line 37: / Line 39: @@
    $G_TMP/gfxtest/gfxtest-treeinit-output.txt
    gfxtest-$testcount-$testName-output.txt
 [[Category:HOWTO]][[Category:$G]][[Category:Software Development]]

Brad Berg at 17:43, 8 January 2009

2009-01-08T17:43:30Z

← Older revision		Revision as of 17:43, 8 January 2009
Line 34:		Line 34:
	* Output Files created on each test machine:		* Output Files created on each test machine:

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

			[[Category:HOWTO]][[Category:$G]][[Category:Software Development]]

Brad Berg: New page: <<< 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??? s...

2009-01-08T17:41:06Z

New page: <<< 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??? s...

New page

<<< 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