Localization testing is the process for checking the localized version of a product for a particular culture or locale setting. Before performing localization testing, it is important to understand two related processes, i.e. globalization and internationalization.
Globalization testing is the process to check whether the software can perform properly in any locale or culture. It is also used to check if the software can function with all types of international inputs. It is commonly called `G11N’ as there as 11 characters in-between the alphabets G & N.
Internationalization testing, on the other hand, is the process of testing software to ensure that it works uniformly across multiple regions and cultures.
Localization testing is the testing process to validate whether an application is capable for use in a particular location or country. It is also called as “`L10N’ as there are 10 characters in-between the alphabets L & N.
In general terms:
- Internationalization is a pre-requisite for localization
- Internationalization and localization are components of globalization
- Translation is a facet of localization
Localization testing will always be done prior to a product or service being launched internationally.
Given below are a few points to remember when performing localization testing:
- Earlier translated products are available for reference
- Glossaries are available for reference and consistency checked
- Domain knowledge about the product, provided to testers
- Data and time format will change based on region
- Phone number formats need to be formatted for a particular region
- License and product key information obey country specific regulations
- Currency conversions and formats are incorporated
- Colors for symbols and UI are allocated for particular region(s)
- Units of measurements, taxes, are in line with the norms of that country to ensure acceptability.
Language Specific Testing:
- Translation is an important facet of localizing content and it is important to ensure that terminology is consistent across user interface.
- Text is free of grammatical mistakes, translated well and is free of character consumption
- Lack of translation is replaced by English by default
- Translation regularly updated for new features in UI
- Localized images are of good quality
- Layout is consistent with the source/English version
- Link breaks and hyphenation are correct
- Basic functionality tests should be performed on the localized application
- Hyperlinks work correctly
- Entry fields support special characters
- Fields are validated. Example, postal codes for target regions
- Lists are sorted according to target language and region
Read Other Blog on G11N Testing