Megatest

@@ -396,10 +407,13 @@ + @@ -411,10 +425,13 @@ + @@ -426,25 +443,49 @@ + + + + + + + + + + @@ -456,10 +497,13 @@ + @@ -473,10 +517,13 @@ + @@ -486,10 +533,13 @@ + @@ -501,18 +551,222 @@ + + +

variable	value +	+required	comment
max_concurrent_jobs	if variable is not defined no limit on jobs +	+no
executable	full path to megatest binary +	+no	Use only if necessary, megatest will extract the location from where it used to launch and add append that to the PATH for test runs.
+ +	+runsdir +	+full path to where the link tree to all runs will be created +	+no +	+Because your runs may be spread out over several disk partitions a central link tree is created to make finding all the runs easy. +
[fields]	string of letters, numbers and underscore	string of letters, numbers and underscore +	+at least one
launcher	command line used to launch jobs - the job command (megatest -execute) will be appended to this +	+no
list of hostnames to run jobs on NOT SUPPORTED RIGHT NOW	+n/a +
string of letters, numbers and underscore	any string +	+no	These are set on the test launching machine, not the test running machine. Typical usage is to control the host or run queue for launching tests. These values will not be seen by the test when it runs.
string of letters, numbers and underscore	a valid path writable by the test launching process and by the test process +	+yes	The disk usage balancing algorithm is to choose the disk with the least space for each test run.

+0.3.2.2 runconfigs.config file +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +

+section +	+variable +	+value +	+required? +	+comment +
+[default] +	+string of letters, numbers and underscore +	+any +	+no +	+variables set in this section will be available for all runs, defining the same variable in another section will override the value from the default section +
+[field1value/field2value...] +	+string of letters, numbers and underscore +	+any +	+no +	+the values in this section will be set for any run where field1 is field1value, field2 is field2value and fieldN is fieldNvalue. +

+Example: a test suite that checks that a piece of software works correctly for different customer configurations and locations each of which is done as a separate release regression run. The fields, CUSTOMER and LOCATION were chosen. The following runconfigs.config file would set some variables specific to runs for megacorp in India and femtocorp in the Cook Islands and New Zealand: +

+0.3.3 Writing tests +

+0.3.3.1 testconfig file +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+section +	+variable +	+value +	+required? +	+comments +
+[setup] +	+runscript +	+name of script to execute for this test +	+yes +	+The script must be executable and either provide the full path or put a copy at the top of your test directory +
+[requirements] +	+waiton +	+list of valid test names +	+no +	+This test will not run until the named tests are state completed and status PASS +
+[items] +	+any valid +	+list of values +	+no +	+The test will be repeated once for each item with the variable name set to the value. If there is more than one variable then the test will be run against all unique combinations of the values +

-0.3.2 megatest.config settings +0.3.2 Configuration files

-0.3.2.1 [setup] +0.3.2.1 megatest.config

+0.3.2.2 runconfigs.config file +

+0.3.3 Writing tests +

+0.3.3.1 testconfig file +