Hi! André Schnabel wrote:
But I wonder if the localized strings are really used to test functionality in a localized version or if they are used to check if if a string is localized correctly. To make it (hopefully) more clear what I mean ..
Testing means verfication. The prio 1 for test script writers (automators) is to use language independent possibilities to get the testing job done. As you know we have special languages, like the asian ones, where we can not goal without doing language dependent actions.
So .. we might be save in functionality testen even without the localized strings and I'd like to remove thoses strings from places where they are not needed (or at least don't want to add more strings if not necessary for testing of functionality).
Yes, but we have an office application and without correct filter names it makes absolutely no sense to test a L10N. Why did you made the L10N? To get your local names into the application.
FMPOV (from my point of view) it makes sense to document what to do and to centralize the strings. The fallback should be English US to test functionality if it's not translated but a warning should also be thrown if language code <> en_US and there is the Enlish string included.
What do you think about that? Cu, Jogi http://qa.openoffice.org/qatesttool http://wiki.services.openoffice.org/wiki/User:Jsi -- =============================================================== Sun Microsystems GmbH Joerg Sievers 20097 Hamburg Quality Assurance Engineer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
