Localization testing should focus on several general areas. The first
involves things that are often altered during localization, such as the UI and
content files. The second consists of culture-specific, language-specific, and
country-specific areas. Examples include configurable components-such as region
defaults and the default language-as well as language-specific and
region-specific functionality-such as default spelling checkers, speech engines,
and so on. You should also test the availability of drivers for local hardware
and look for the encryption algorithms incorporated into the application. The
rules and regulations for distribution of cryptographic software differ from
country to country.
Pay specific attention to the customization that could not be automated
through the globalization services infrastructure (Win32 NLS APIs and the .NET
Framework). For example, check that formatting of mailing addresses is
locale-specific and that parts of the user's name are ordered correctly. (The
order in which surname and first name appear varies according to country. For
instance, some Muslim countries and certain regions in India use a different
name order than that used in the English language.) Functionality of this kind
is often implemented by an application-testing must verify its correctness.
Other areas of localization testing should include basic functionality tests;
setup, upgrade, and uninstall tests that are run in the localized environment;
and, finally, application and hardware compatibility tests that are planned
according to the product's target market.
