Localization Testing Process

Localization testing process is highly dependent on the particular product that is being localized. The testing methodology for a web localization project will be different than of a software. However, regardless of the product and the platform, localization testing covers the three main areas listed below. The execution process is designed on a case by case basis.

Linguistic testing

Validation of the translated content within context

• Grammatical, spelling, and punctuation errors – is the text free of linguistic errors?
• Accuracy of translation in the given context – does translation fit within given context? The translation of a single word may change within the context. The terms Exit and Close may indicate the same operation in some cases; however, the translation will depend on the action that the word refers to. Only way to ensure proper translation is to see the actual button.
• Adherence to glossary – is the translation consistent with the provided glossary? Is it consistent throughout the application? Are brand names translated correctly?
• Missing content – is the localized content imported properly and entirely to the UI? Is everything translated?

Cosmetic testing – “look and feel” review

Cosmetic testing is a crucial part of the localization testing process as unexpected problems may occur due to text expansion and other UI changes

• Consistent layout with source – do images, tables, and general design matches the source product?
• Translation consistency – is the terminology consistent across graphics, documentation, and the UI? For example, if the instructions say “Click on the Agree button to move forward,” users expect to see the word “Agree” on the button – not “OK.”
• Correct line breaks – is the text broken in the correct place? Automated text wrapping can often break words or sentences in incorrect places, separating one character from the rest of the word. In some languages, such as Thai, only a person who can read the language is capable of verifying if a line break is correct.
• Layout – are there any truncation issues? Is the text aligned properly?
• Display – are there any character corruption issues?

Functional testing – Functional validation of localized product

Functional testing is usually not necessary for document translation projects except for interactive pdfs and online help

• Install, use, uninstall – is the application fully functional on a localized operating system?
• Supported platforms – does the web application function properly on localized versions of the supported browsers?
• Review – are all hyperlinks functional? Do they point to the correct pages? Is data sorted properly? Do the cascading list boxes work as expected?
• Input/output validation – do the input fields allow the use of non ASCII characters? Are the non ASCII characters displayed back to the user properly after being saved to the database?
• Regional formatting – is the display format proper for date/time? Does the calendar start from the correct day?
• Hotkeys/shortcut keys – are they functional?

This is a brief summary of our localization testing process and coverage. Please contact us at [email protected] for a free customized testing process consultation and request our localization testing checklist!