Table of Contents
@@ -202,56 +191,65 @@
Subsection 6.2: Rewrite your main.csh for iteration
+
+
-
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-Subsubsection 8.5.2: Command line
+Section 8: Generating an OpenDocument Spreadsheet from the Database
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Section A: Data
@@ -612,29 +610,114 @@
+6.4 Rolling up Miscellaneous Data +
+
+Use the -load-test-data switch to roll up arbitrary data from a test into the test_data table.
+
+
+
+
+
+
+# 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 ++
+New entries are keyed on the category and variable. If a new record is inserted with a category and variable that have already been used the new record will replace the old record.
+
+
+Where value, expected and tol are specified the behavior is as follows.
+
+-
+
- +If value, expected and tol are numbers then status is calculated as PASS if (expected-tol) <= value <= (expected+tol) + +
- +If value and expected are numbers and tol is >, <, >= or <= then value is compared with expected using the operator given by tol + +
- +If status is specified its value overrides the above calculations. + + +
+6.5 Rolling up Runs +
+
+To roll up a number of tests in a sequence of runs to a single run use the -rollup command.
+
+
+
+
+
+
+megatest -rollup :sysname ubuntu :fsname nfs :datapath none :runname rollup_ww38 ++
+All keys must be specified and the runname is the name of the run that will be created. All paths are kept original inside the database. When -remove-runs is used to delete runs the data is not deleted if there are rollups that refer to the data.
+
7 Dashboard
+
+
+
+
+> dashboard & ++
+Pushing one of the buttons on the main dashboard will bring up the test specific dashboard. Values are updated in semi-real time as the test runs.
+
-8 Reference +8 Generating an OpenDocument Spreadsheet from the Database +
+
+And OpenDocument multi-paned spreadsheet can be generated from the megatest.db file by running -extract-ods
+
+
+
+
+
+
+megatest -extract-ods results.ods :runname % ++
+You can optionally specify the keys for your database to limit further the runs to extract into the spreadsheet. The first sheet contains all the run data and subsequent sheets contain data rolled up for the individual tests.
+
++9 Reference
-8.1 Configuration file Syntax +9.1 Configuration file Syntax
-8.1.1 Sections +9.1.1 Sections
[section name]@@ -643,11 +726,11 @@
This creates a section named “section name”
-8.1.2 Variables +9.1.2 Variables
VARX has this value@@ -656,11 +739,11 @@
The variable “VARX” will have the value “has this value”
-8.1.3 Includes +9.1.3 Includes
[include filename]@@ -669,11 +752,11 @@
The file named “filename” will be included as if part of the calling file. NOTE: This means no section can be named “include “ (with the whitespace).
-8.1.4 Setting a variable by running a command +9.1.4 Setting a variable by running a command
VARNAME [system ls /tmp]@@ -682,11 +765,11 @@
The variable “VARNAME” will get a value created by the Unix command “ls /tmp”. All lines of output from the command will be joined with a space.
-8.1.5 Notes +9.1.5 Notes
- Some variables are infered as lists. Each token on the line separated by whitespace will be member of the list. @@ -694,11 +777,11 @@ Comments (lines starting with #) and blank lines are ignored.
-8.2 Environment variables +9.2 Environment variables
| @@ -784,11 +867,11 @@ |
-8.3 megatest.config +9.3 megatest.config
| @@ -955,11 +1038,11 @@ |