# Fields are the keys under which your test runs are organized
[fields]
field1 TEXT
field2 TEXT
​
[jobtools]
# The launcher launches jobs to the local or remote hosts,
# the job is managed on the target host by megatest,
# comment out launcher to run local only. An example launcher
# "nbfake" can be found in the utils directory. 
launcher nbfake
​
# The disks section specifies where the tests will be run. As you
# run out of space in a partition you can add additional disks
# entries.
# Format is:
# name /path/to/area 
[disks]
disk1 /tmp 

# runconfigs.config

../tests
  ├── megatest.config
  ├── runconfigs.config
  └── tests
     └── mytest
           ├── main.sh
           └── testconfig

[setup]
runscript main.sh

#!/bin/bash
​
$MT_MEGATEST -runstep mystep1 "sleep 20;echo Done" -m "mystep1 is done"
$MT_MEGATEST -test-status :state COMPLETED :status PASS -m "This is a comment"

megatest :field1 abc :field2 def :runname 2011week08.4a -runall
​
watch megatest -list-runs %
​
# OR use the dashboard
​
dashboard &

mkdir simpletest
cd simpletest

# testconfig
​
[setup]
runscript main.csh

#!/bin/tcsh -x
​
# run the cpu1 simulation.
#   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"
$MT_MEGATEST -test-status :state COMPLETED :status $?

#!/bin/tcsh -x
​
# run the cpu1 simulation.
#   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_cpu1 -logpro runsim.logpro "runsim cpu1" && \
$MT_MEGATEST -runstep run_simulation_cpu2 -logpro runsim.logpro "runsim cpu2"
$MT_MEGATEST -test-status :state COMPLETED :status $?

# Example Makefile to run two steps in parallel
​
RTLDIR=/path/to/rtl
CPUS = cpu1 cpu2
​
run_simulation_$(CPUS).html : $(RTLDIR)/$(CPUS)
	$(MT_MEGATEST) -runstep run_simulation_$(CPUS) -logpro runsim.logpro "runsim $(CPUS)

#!/bin/tcsh -x
​
# run the cpu1 and cpu2 simulations in parallel. 
# The -j parameter tells make how many jobs it may run in parallel
​

make -j 2 


$MT_MEGATEST -test-status :state COMPLETED :status $?

[setup]
runscript main.csh




[items]
CPU cpu1 cpu2

#!/bin/tcsh -x







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



# 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 $?

# testconfig for the "system" test



[setup]



runscript main.csh



waiton cpu mem

# Fields are:
# category,variable,value,expected,tol,units,comment,status
​
$MT_MEGATEST -load-test-data << EOF
foo,bar,1.2,1.9,>
foo,rab,1.0e9,10e9,1e9
foo,bla,1.2,1.9,<
foo,bal,1.2,1.2,<,,Check for overload
foo,alb,1.2,1.2,<=,Amps,This is the high power circuit test
foo,abl,1.2,1.3,0.1
foo,bra,1.2,pass,silly stuff
faz,bar,10,8mA,,,"this is a comment"
EOF

megatest -rollup :sysname ubuntu :fsname nfs :datapath none :runname rollup_ww38

> dashboard &

megatest -extract-ods results.ods :runname % 

[section name]

VARX has this value

[include filename]

VARNAME [system ls /tmp]

# 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