← QA Library
Chapter 14 / 19 · 6 min read

Localisation and internationalisation testing

How to test a product in several languages and regions: translations, formats, layouts, right-to-left scripts and cultural details.

Internationalisation (i18n) is designing a product so it can be adapted to any language and region. Localisation (l10n) is the actual adaptation: translation, formats, content. Testers check both — that the product is technically ready for other languages, and that each language version is correct and natural.

What to check

AreaTypical problems
TranslationsMissing strings, untranslated text in images, wrong context (“Save” as in rescue instead of store)
Text lengthGerman and Ukrainian are often 30–40% longer than English; buttons overflow or text gets cut
Plurals“1 items”, wrong forms in languages with several plural forms (Ukrainian: 1 файл, 2 файли, 5 файлів)
Dates and times03/04 means March 4 in the US and 3 April in Europe; time zones and 12/24 h
Numbers and currency1,000.50 vs 1 000,50 vs 1.000,50; currency symbol position
Sorting and searchAlphabetical order of Ä, Ł, Є; case-insensitive search for non-Latin letters
InputNames with apostrophes and hyphens, non-Latin addresses, phone formats
Right-to-leftArabic and Hebrew mirror the layout; icons and arrows must flip correctly

Pseudo-localisation

Before real translations exist, replace every string with a longer, accented version: Save → [Šåvé ~~~~]. It immediately reveals hard-coded text that wasn't sent for translation, layouts that break with longer words, and characters the font can't display.

Language switching and SEO

  • The language switcher keeps the user on the same page
  • The chosen language is remembered
  • Each language has its own URL and the page declares its language (<html lang>)
  • hreflang links tell search engines about the other versions
  • Emails, notifications, PDFs and error messages are translated too — not just the website

Cultural details

Colours, gestures, images, humour, holidays and examples can mean different things in different markets. Payment methods, address formats and legal texts also vary by country. A native speaker's review of the final product, in context, is the best way to catch text that is technically correct but sounds unnatural.

Test with real content in every language, on real screen sizes. Translations that look fine in a spreadsheet can still break on a 360-pixel-wide phone.