`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)
$ cd toto
> TOTO
- $ cat > file
+ $ mkfile file
TOTO will be passed to the cd command, where the user clearly want to pass it
-to cat.
+to the mkfile buildin command (see below).
+
+Stream redirection
+------------------
+Stream redirections (">", "<" and "|" constructs in sh) are not
+implemented yet in tesh. This is a bit restrictive, but well, patch
+welcome...
+
+The situation in which it is mainly problematic is to create a
+temporary file. The solution is to use the "mkfile" buildin command,
+as in the following example:
+$ mkfile myFile
+> some content
+> to the file
+
+This will create a file called myFile (first argument of the mkfile
+command). Its content will be all the input provided to the command.
RETURN CODE
-----------
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
