Valiables with a LocalizedText value can be written, but by writing a new value, the server may !!! simply add a translation if the locale differs from the actual value.
However a server is also allowed to replace the complete LoclizeText with the written value.
E.g.
Actual value == "en","Hello"
Write value == "", Hello world"
=> The server stores both locales, the empty and the "en"

Reading the value back will result in either "en", "Hello" or in "", "Hello world", depending on the preferred locales of the session.

The tests in "Attribute Services" - "Attribute Write Index" seem not aware of this behaviour.
Affected are test scripts 001, 002, 003, 004, 005

The tests are writing value "", "mocalizedText1" (typo!) and get back a LocalizedText with locale "en".

Possible solution:

• write localized texts in the locale of the actual value
• specify a preferred locale at session to match the locale written