`<' input to pass to the command
`>' output expected from the command
`!' metacommand, which can be one of:
- `set timeout' <integer>
+ `timeout' <integer>|no
`expect signal' <signal name>
`expect return' <integer>
`output' <ignore|display>
+ `setenv <key>=<val>'
`p' a string to print
`P' a string to print at the CRITICAL level (ease logging grepping)
-----------
TESH spits an appropriate error message when the child do not return 0 as
-return code (cf. catch-return.tesh).
+return code (cf. catch-return.tesh), and returns code+40 itself.
It is also possible to specify that a given command must return another
value. For this, use the "expect return" metacommand, which takes an integer as
--------
By default, all commands are given 5 seconds to execute
-(cf. catch-timeout.tesh). You can change this with the "set timeout", which
+(cf. catch-timeout.tesh). You can change this with the "timeout", which
takes an integer as argument. The change only apply to the next command
-(cf. set-timeout.tesh).
+(cf. set-timeout.tesh). If you pass "no" as argument, the command
+cannot timeout.
OUTPUT
------
By default, the commands output is matched against the one expected,
and an error is raised on discrepency. Metacomands to change this:
"output ignore" -> output completely discarded
- "output display" -> output displayed (but not verified)
\ No newline at end of file
+ "output display" -> output displayed (but not verified)
+
+ENVIRONMENT
+-----------
+You can add some content to the tested processes environment with the
+setenv metacommand. It works as expected. For example:
+ "setenv PATH=/bin"
\ No newline at end of file
