Software tests - Revision history

Wesley Miller: /* Running Tests */

2013-12-22T05:53:47Z

Running Tests

← Older revision		Revision as of 05:53, 22 December 2013
Line 4:		Line 4:

	If you want to perform a private test run and suppress mail notifications run:		If you want to perform a private test run and suppress mail notifications run:

			<pre>
			$ ./common/build/valid/test.platform.py -noemail
			</pre>

	<pre>		<pre>

Brad Berg at 15:25, 4 April 2012

2012-04-04T15:25:43Z

← Older revision		Revision as of 15:25, 4 April 2012
Line 48:		Line 48:

	== Test System Maintenance ==		== Test System Maintenance ==

			THe directories and files manages by tStaff are:

	/tstaff/bin/regtest # tStaff manages the driver.		/tstaff/bin/regtest # tStaff manages the driver.
Line 84:		Line 86:
	#		#
	> systest-link /systest/projects/<project>/<test_name>.<suffix> /systest/bin/<test_name>		> systest-link /systest/projects/<project>/<test_name>.<suffix> /systest/bin/<test_name>


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

Brad Berg at 15:24, 4 April 2012

2012-04-04T15:24:03Z

← Older revision		Revision as of 15:24, 4 April 2012
Line 46:		Line 46:
	Large raw input files such as MRI images should be copied to a directory named <tt>$GROOT/data/<project>/test/</tt>. Cooked data and test output should go to a test directory inside the project directory. Tests should clear output files from prior runs to avoid false positives. Regression tests that use diff to check output should comapare against a file named: <tt><root name>_base.<suffix></tt>		Large raw input files such as MRI images should be copied to a directory named <tt>$GROOT/data/<project>/test/</tt>. Cooked data and test output should go to a test directory inside the project directory. Tests should clear output files from prior runs to avoid false positives. Regression tests that use diff to check output should comapare against a file named: <tt><root name>_base.<suffix></tt>


			== Test System Maintenance ==

			/tstaff/bin/regtest # tStaff manages the driver.
			/systest/bin/* # Run only the links; excludes other files.

			/systest/bin/: Changes are reflected to all department machines.
			The build64 and build32 machines have separate test links.

			Systest commands:

			> systest-info -A # print all project info
			CTime: 1235158613
			Description: Test software for the VRL group.
			Links: bin/vrl_test
			MTime: 1236091161
			Name: vrltest
			Owners: bb dhl


			# Select project: To add type in a project name and hit "Create".
			# Create Project: Description: Enter a brief description.
			# Owners: Enter space separated user ids.
			# Prject name = vrl -> creates /systest/projects/vrl
			#
			> systest-req # Interactive box to add a new project (run on Linux box).


			# Run after creating a new project and set up a test script:
			# add: /systest/projects/<project>/<test>.<suffix>
			#
			> systest-link /systest/projects/<project>/<test_name>.<suffix> /systest/bin/<test_name>


			# Run after creating a new project and set up a test script:
			# add: /systest/projects/<project>/<test>.<suffix>
			#
			> systest-link /systest/projects/<project>/<test_name>.<suffix> /systest/bin/<test_name>

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

Brad Berg: /* Running Tests */

2010-04-23T14:11:48Z

Running Tests

← Older revision		Revision as of 14:11, 23 April 2010
Line 12:		Line 12:

	<pre>		<pre>
	> /systest/bin/~~vrl_test~~ -config <My work area>/<Custom configuration>.cfg		> /systest/bin/vrl_fast -config <My work area>/<Custom configuration>.cfg
	</pre>		</pre>

Brad Berg: /* Running Tests */

2010-04-23T14:11:24Z

Running Tests

← Older revision		Revision as of 14:11, 23 April 2010
Line 9:		Line 9:
	</pre>		</pre>

	To run a set of select tests and specify alternative mail notifications (usually to yourself) you can run using a custom configuration file. Make a private copy of the default configuration file and modify it. The comments in the default configuration file describe the format. Then run using the new configuration:		To run a set of select tests and specify alternative mail notifications (usually to yourself) you can create and run using a custom configuration file. Make a private copy of the default configuration file and modify it. The comments in the default configuration file describe the format. Then run using the new configuration:

	<pre>		<pre>

Brad Berg: /* Running Tests */

2010-04-23T14:10:41Z

Running Tests

← Older revision		Revision as of 14:10, 23 April 2010
Line 6:		Line 6:

	<pre>		<pre>
	> /systest/bin/~~vrl_test~~ -noemail		> /systest/bin/vrl_fast -noemail
	</pre>		</pre>

Line 35:		Line 35:
	####################### end test.platform.fast.cfg ##########################		####################### end test.platform.fast.cfg ##########################
	</pre>		</pre>


	== Writing Tests ==		== Writing Tests ==

Brad Berg at 15:45, 21 April 2010

2010-04-21T15:45:17Z

← Older revision		Revision as of 15:45, 21 April 2010
Line 38:		Line 38:

	== Writing Tests ==		== Writing Tests ==

			It is a good idea to provide one or more quick tests that can be included in the test suite we run each night. Tests need to run in batch mode and simply return a zero status if successful and non-zero if they fail.

	Create a make test target that runs a test that returns a zero status for success and a non-zero status for an error. The test should be able to run as a batch job (not interactive). Projects with multiple tests can use a target named <tt>test.<name></tt> for each individual test and a target <tt>alltest</tt> to run them all.		Create a make test target that runs a test that returns a zero status for success and a non-zero status for an error. The test should be able to run as a batch job (not interactive). Projects with multiple tests can use a target named <tt>test.<name></tt> for each individual test and a target <tt>alltest</tt> to run them all.

Trevor O'Brien: Write and run software tests moved to Software tests

2010-04-19T15:25:31Z

Write and run software tests moved to Software tests

← Older revision	Revision as of 15:25, 19 April 2010
(No difference)

Brad Berg at 14:39, 20 October 2009

2009-10-20T14:39:13Z

← Older revision		Revision as of 14:39, 20 October 2009
Line 1:		Line 1:
	== Running Tests ==		== Running Tests ==

	The test driver is installed on all CS department machines. A configuration file is used to launch tests and mail results to subscribers. You can subscribe to a test summary or receive notices when select tests fail. The default configuration file is: <tt>$G/common/build/~~valid~~/test.platform.cfg</tt>		The test driver is installed on all CS department machines. A configuration file is used to launch tests and mail results to subscribers. You can subscribe to a test summary or receive notices when select tests fail. The default configuration file is: <tt>$G/common/build/site/test.platform.cfg</tt>

	If you want to perform a private test run and suppress mail notifications run:		If you want to perform a private test run and suppress mail notifications run:

Brad Berg at 14:15, 19 August 2009

2009-08-19T14:15:30Z

← Older revision		Revision as of 14:15, 19 August 2009
Line 44:		Line 44:

	Large raw input files such as MRI images should be copied to a directory named <tt>$GROOT/data/<project>/test/</tt>. Cooked data and test output should go to a test directory inside the project directory. Tests should clear output files from prior runs to avoid false positives. Regression tests that use diff to check output should comapare against a file named: <tt><root name>_base.<suffix></tt>		Large raw input files such as MRI images should be copied to a directory named <tt>$GROOT/data/<project>/test/</tt>. Cooked data and test output should go to a test directory inside the project directory. Tests should clear output files from prior runs to avoid false positives. Regression tests that use diff to check output should comapare against a file named: <tt><root name>_base.<suffix></tt>


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