Revision: 3852
Author: pekka.klarck
Date: Thu Aug 19 05:32:21 2010
Log: oooops, setting invalid values to environment variables on the running
side without resetting them isn't such a good idea
http://code.google.com/p/robotframework/source/detail?r=3852
Modified:
/trunk/atest/robot/cli/monitor/encoding_from_env_vars.txt
=======================================
--- /trunk/atest/robot/cli/monitor/encoding_from_env_vars.txt Thu Aug 19
04:41:42 2010
+++ /trunk/atest/robot/cli/monitor/encoding_from_env_vars.txt Thu Aug 19
05:32:21 2010
@@ -10,7 +10,6 @@
*** Test Cases ***
Invalid Encoding In Environment Variables
- Set Invalid Environment Variables
${stdout} ${stderr} = Run Some Tests With Std Streams Redirected
Should Contain ${stdout} Pass And Fail :: Some tests here
Should Be Empty ${stderr}
@@ -18,14 +17,11 @@
*** Keywords ***
-Set Invalid Environment Variables
- :FOR ${var} IN LANG LC_TYPE LANGUAGE LC_ALL
- \ Set Environment Variable ${var} invalid
-
Run Some Tests With Std Streams Redirected
Set Runners
${cmd} = Catenate
... echo "redirect stdin" |
+ ... LANG=invalid LC_TYPE=invalid LANGUAGE=invalid LC_ALL=invalid
... ${ROBOT} --monitorcolors off ${TESTFILE}
... > ${STDOUT FILE} 2> ${STDERR FILE}
Run ${cmd}
