Internationalization Testing (i18n Testing)
Testing that software can handle any language or locale, before actual translation.
Definition
Internationalization testing verifies that software is properly prepared for localization—that it can handle any language without code changes. Tests include: character encoding support, text expansion/contraction, date/number formatting, RTL layouts, and externalized strings. i18n testing happens before translation, using pseudo-localization and locale switching.
Examples
- →Encoding: Japanese, Chinese, Arabic characters display correctly
- →Expansion: UI accommodates 50% longer German text
- →RTL: layout mirrors properly for Arabic/Hebrew
- →Formatting: dates/numbers respect locale settings
Frequently Asked Questions
How do I test i18n without translators?
Use pseudo-localization to simulate translated strings. Test with different locales in browser/OS. Use extended characters (Japanese, Arabic) in forms. Check date/number formatting by switching locales. Tools like i18n-checker can scan for issues.
What are common i18n bugs?
Common issues: hardcoded strings missed for extraction, concatenation breaking sentence structure, truncated text, mojibake from encoding issues, assumptions about text direction, date format confusion (MM/DD vs DD/MM), broken layouts with long text.