Able, Irectives in the configuration file – ADLINK aTCA-N700 User Manual
Page 66
aTCA-N700 SW Users Guide
60
Table 9-1 Directives in the configuration file
Directive
Function
Remark
#
Start character of comment
line
<$STRING>
Defines a Test item.
The directives after this one
until next “<>” or “[]” become
the attribute of the Test Item.
[$STRING]
Defines a Test module.
The directives after this one
until next “<>” or “[]” become
the attribute of the Test
module.
device: $STRING
Defines a device to test.
extern: (yes:no)
Defines the Test program:
either nbm_diag or an external
program.
Default: no
intrusiveness:
(yes|no)
Defines intrusiveness.
Default: no
test_item: $STRING
Defines nbm_diag built-in test
item.
Usable only with “tester: self”.
nbm_diag built-in test item list
is checked by “nbm_diag –l”.
test_exec: $LINE
Defines an execution file and
options for the test.
Usable only with “tester:
other”
test_prepare: $LINE
Defines an execution file and
options for test preparation
before the test.
Usable only with “tester:
other”
test_finish: $LINE
Defines an execution file and
options to recover the status
after the test.
Usable only with “tester:
other”
test_log: $STRING
Defines a log file when the
Test program generates one.
Log file may be used for the
test result data.
test_result:
$STRING
Defines a result file of external
program including an err log
when the Test program
generates one.
Usable only with “tester:
other”
See the syntax for test result
Without this, return value shall
be the result of the test.
default test_result file is
/tmp/nbm_diag_result.txt
Each test module contains one or more test items, which are configurable. The tested
results are stored in the test_result file.
The commands used with an external command have restrictions on stdin/stdout use
because the test execution is converted as the following.
test_exec: ls –la
converted
to
“ls –la > /dev/null 2>&1”
test_exec: ls –la; echo 1234
converted
to
“ls –la > /dev/null 2>&1; echo 1234 > /dev/null 2>&1”