Localization testing ensures defects are identified and resolved
– before your users find them for you

TranslationLoft | Localization Testing
Localization Testing

Test out your localized products before they go live

Localization testing is a crucial phase of the localization process and is integral to ensuring that your localized product is as good as it possibly can be, while also avoiding the significant cost of resolving errors that come to light after they have reached your live environment.

Localization testing is more than just linguistic testing. It is a valuable opportunity to validate and refine your code release process. Does your localized code correctly bundle any new localization files? And is there any related server configuration required? Such issues are flushed out during localization testing and lessons learned can be incorporated into the live release process, ensuring problems don’t reoccur for your users.

Localization testing is in-context testing – that is to say, our in-country, native-speaking testers use appropriate browsers and/or devices to replicate real user behaviour and test at the necessary coverage level to ensure zero defects. Localization defects can take many forms, but in the main, we check for the following:

  • Translation quality – In-context testing allows our linguistic reviewers to view all translated screen content in context. UI components are reviewed just as they will appear to real users, and any translation inaccuracies resulting from lack of context are immediately apparent to linguistic testers. An example could be where the English word "Home" has been translated as "where you live", which can indeed be correct. However, when applied to a website, the meaning is different, and when viewed in context, the error is immediately apparent.
  • Is your target locale correctly supported? Does the content correctly display dates, times, and currencies?
  • Has UTF-8 encoding been correctly implemented? i.e. do all non-standard characters display correctly?
  • Is there any content that hasn’t been translated? For example, hard-coded literal content in application code that didn’t make it to the resource bundle.
  • Is there any content that has been translated and should not have been? For example, strings containing brand names that were incorrectly included in the resource bundle and sent for translation.
  • Has there been any impact on UI layout because of expanded text? For example, a button may have been sized to accommodate the word "Go" and when translated into German as "Ausführen", is too short for its label.
  • Are there any images with embedded text that may have been missed? Images identified at this stage need to be re-worked.
  • Are there any code syntax errors where content was correctly retrieved from a resource bundle, but because of a concatenation or word order issue, is displayed incorrectly for a particular language?