@@ -365,16 +365,11 @@ # The step name is "run_simulation" # The commandline being run for this step is "runsim cpu1" # The logpro file to validate the output from the run is "runsim.logpro" ​ $MT_MEGATEST -runstep run_simulation -logpro runsim.logpro "runsim cpu1" -if ($? == 0) - set status = PASS -else - set status = FAIL -end -$MT_MEGATEST -test-status :state COMPLETED :status $status +$MT_MEGATEST -test-status :state COMPLETED :status $?
@@ -395,16 +390,11 @@ # The commandline being run for this step is "runsim cpu1" # The logpro file to validate the output from the run is "runsim.logpro" ​ $MT_MEGATEST -runstep run_simulation_cpu1 -logpro runsim.logpro "runsim cpu1" && \ $MT_MEGATEST -runstep run_simulation_cpu2 -logpro runsim.logpro "runsim cpu2" -if ($? == 0) - set status = PASS -else - set status = FAIL -end -$MT_MEGATEST -test-status :state COMPLETED :status $status +$MT_MEGATEST -test-status :state COMPLETED :status $?

@@ -438,16 +428,11 @@ ​ # run the cpu1 and cpu2 simulations in parallel. # The -j parameter tells make how many jobs it may run in parallel ​ make -j 2 -if ($? == 0) - set status = PASS -else - set status = FAIL -end -$MT_MEGATEST -test-status :state COMPLETED :status $status +$MT_MEGATEST -test-status :state COMPLETED :status $?

@@ -479,16 +464,14 @@ ​ # run the cpu simulation but now use the environment variable $CPU # to select what cpu to run the simulation against ​ $MT_MEGATEST -runstep run_simulation -logpro runsim.logpro "runsim $CPU" -if ($? == 0) - set status = PASS -else - set status = FAIL -end -$MT_MEGATEST -test-status :state COMPLETED :status $status +# As of version 1.07 Megatest automatically converts a status of "0" +# to "PASS", any other number to "FAIL" and directly uses the value of +# a string passed in. +$MT_MEGATEST -test-status :state COMPLETED :status $?

@@ -916,57 +899,31 @@
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:
-
-# runconfigs.config -
-
-[default] -
-
-ENCRYTION true -
-
-# -
-
-[megacorp/india] -
-
-TESTPATH /nfs/testing/megacorp_runs -
-
-# -
-
-[femtocorp/cook_islands] -
-
-ENCRYTION false -
-
-TESTPATH /afs/kiatoa/testing/cook_islands -
-
-# -
-
-[femtocorp/new_zealand] -
-
-TESTPATH /afs/kiatao/testing/new_zealand -
-
-# -
-
-[megacorp/new_zealand] -
-
-TESTPATH /nfs/testing/megacorp_runs +
+
+
# runconfigs.config
+[default]
+ENCRYTION true
+​
+[megacorp/india]
+TESTPATH /nfs/testing/megacorp_runs
+​
+[femtocorp/cook_islands]
+ENCRYTION false
+TESTPATH /afs/kiatoa/testing/cook_islands
+​
+[femtocorp/new_zealand]
+TESTPATH /afs/kiatoa/testing/new_zealand
+​
+[megacorp/new_zealand]
+TESTPATH /nfs/testing/megacorp_runs
+
+
+
Running megatest like this:
@@ -1208,14 +1165,14 @@ :runname - +[a-zA-Z0-9_-]+ - +directory in which this run will be stored in the test run area @@ -1223,44 +1180,44 @@ :state - +any value - +Set the step or test state, this is stored in the state field in the steps or tests table respectively - +For tests Megatest recognises “INCOMPLETE”, “COMPLETE” :status - +any value - +Set the step or test status, this is stored in the status field in the steps or tests table respectively - +For tests Megatest recognises “PASS”, “FAIL”, and “CHECK” -list-runs - +any value, % is wildcard - +Respects -itempatt and -testpatt for filters @@ -1268,11 +1225,11 @@ -testpatt - +any value, % is wildcard @@ -1283,11 +1240,11 @@ -itempatt - +any value, % is wildcard @@ -1301,11 +1258,11 @@ - +Print the keys being used for this database @@ -1316,14 +1273,14 @@ - +Test will not re-run if in the “PASS”, “CHECK” or “KILLED”, using -force will force the run to be launched. - +WARNING: The -force switch will bypass any “waiton” dependencies. @@ -1331,11 +1288,11 @@ - +Launch an xterm instead of run the test. The xterm will have the environment that the test would see. @@ -1346,11 +1303,11 @@ - +Remove a run, test or subtest from the database and the disk. Cannot be undone. Requires -testpatt, -itempatt, :runname and all keys be specified. @@ -1376,11 +1333,11 @@ - +Used inside a test to run a step, record the start and end of the step and optionally analyze the output using logpro. @@ -1391,11 +1348,11 @@ - +If using logpro to asses the PASS/FAIL status of the step you specify the logpro file with this parameter. @@ -1405,10 +1362,10 @@