| || |
Any weird results from ST 2006 R2 Patch 1 UTF-8 ?
Today I did get one. (using the UTF-8 format)
NOTE: the same testcase runs successfully all the time before switching to the UTF-8 format.
Part of my testcase has:
sExpected = "the expected error message"
*** Error: Variable (sExpected) has not been set
- Selected the line - sExpected = "the expected error message"
- Copied and Pasted the selected line to the very next line
- Deleted the original line
- Re-ran the test and boom --- Test passed!
.inc and .t files were loaded into SilkTest 2006 R2 Patch 1 version followed by File/Save As and changing the format from ANSI to UTF-8.
Is it safer to use the Unicode format instead?
If you happen to run into any weird results when using the UTF-8 format, please don't hesitate to post your results.
Re: Any weird results from ST 2006 R2 Patch 1 UTF-8 ?
Here's another one...
TypeKeys ("DATE") sometimes results to typing "dATE" instead of "DATE".
..I wonder if the UNICODE format is any better than UTF-8 !?