action scripts are executed after a test set is run, regardless
of the exit state of the test set.
They decide what to do by themselves based on the value of the
overall test result provided in
$TS_RESULT.
They have to be placed into the actions
subdirectory of the test set (typically symlinked to
${HC_TESTSET_PATH}/all/actions/*).
Scripts without the execution bit set as well as those with
names matching the regular expression
(^[^a-zA-Z0-9])|(~$)|(\.bak$)|(\.orig$)|(\.rpmnew$)|(\.rpmorig$)|(\.rpmsave$)
are silently ignored.
A number of environment variables are passed to the action script:
TESTSET
The name of the test set.
0, which means no timeout.
TS_RESULT
The result of the testset. (0 = OK, 1 = WARNING, 2 = ERROR)
TS_COUNT_TOTAL,
TS_COUNT_OK,
TS_COUNT_WARN,
TS_COUNT_ERR
Total number of tests run or number of tests which returned OK, WARNING or ERROR, respectively.
TS_LIST_OK,
TS_LIST_WARN,
TS_LIST_ERR
Comma-separated lists of tests returning OK, WARNING or ERROR, respectively.
For a typical action script, refer to Appendix D.