X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/4f6a20c70493120df0f813a6832d69d35c6f5a7c..f22fa286e259aad98dd2e0e37e39fa7e89151ae4:/tools/tesh/README.tesh diff --git a/tools/tesh/README.tesh b/tools/tesh/README.tesh index 9d78a15e20..5eb44e87c8 100644 --- a/tools/tesh/README.tesh +++ b/tools/tesh/README.tesh @@ -18,6 +18,7 @@ blank and is ignored): `expect signal' `expect return' `output' + `setenv =' `p' a string to print `P' a string to print at the CRITICAL level (ease logging grepping) @@ -56,7 +57,7 @@ RETURN CODE ----------- 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 @@ -87,4 +88,10 @@ 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