Localization Test is the process of adapting a globalized application to a particular culture/locale. Localizing an application requires a basic understanding of the sets of character commonly employed in modern software development and an apprehension of the risks associated with them.
Localization testing contains the translation of the application user interface and adapting graphics for a particular culture/locale. The localisation process can also include translating any help content associated with the application program into native language.
Localisation of business solutions needs that you implement the correct business processes and practices for a culture/locale. Differences in how cultures/locales conduct business are to a great extent determined by governmental and regulatory requirements. Hence, localisation of business logic can be a big task.
”Localisation testing” checks how well the build has been interpreted into a particular target language. This test is founded on the results of globalized validation where the functional support for that particular locale has already been validated. Whenever the product is not globalised enough to support a given language, you probably will not try to focalise it into that language in the first place!
You still have to check that the application you’re shipping to a specific market actually works and the following section shows you some of the common areas on which to focus when executing a Localization of test.
Things which are often altered during localization, such as the user interfaces and content files. Below is a Localization testing checklist:
– Key boards
– Text Filters
– Hot keys
– Spelling Rules
– Sorting Rules
– Upper and Lower case conversions
– Size of Papers
– Date formats
– Measurements and Rulers
– Available memory
– It is as well a good idea to test that everything you are going to distribute in a local market complies with the local laws and regulations.