| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
SET Statement |
| |
- Test invalid combinations (Group -> Unicode/National, Unicode/National -> Group), is error message understandable?
- For each of the types (Date, Format, Logic, Numeric, Text, Token), perform 4 tests: move from type into Unicode, move from type into National, move from Unicode into type, move from National into type.
|
|
<
< |
- Test Raw to National (with/without transcode error)
- Test Raw to Unicode
- Test National to Raw (with/without transcode error)
- Test Unicode to Raw (with/without transcode error)
|
>
> |
- Test Raw to National and back (with/without transcode error)
- Test Raw to Unicode and back (with/without transcode error)
|
| |
- Test Unicode to Unicode
- Test National to National
|
|
<
< |
- Test Unicode to National
- Test National to Unicode
|
>
> |
- Test Unicode to National and back (with/without transcode error)
- Test National to Unicode and back (with/without transcode error)
|
| |
- Test Truncation & padding
Bugs |
| |
- SETing a National field back into a Token does not work, just get ???????
- SETing a Unicode field back into a Token does not work, just get ???????
- Does not throw transcode error when moving raw to National when raw contains non national data
|
|
>
> |
- A Raw alpha containing \u#### or \U######## does not get transcoded to Unicode.
- SETing a unicode character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. It should be transcode error.
- SETing a national character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. It should be transcode error.
- SETing a Unicode Character into a National field, where the Unicode character is not part of the National set does not create a transcode error.
|
| |
-
-- SteveFrizzell - 2011-03-07
\ No newline at end of file |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.