Localization Testing
Verifying that localized software works correctly for each target locale.
Definition
Localization testing (L10n testing) verifies that translated software functions correctly and appropriately for each target market. It includes: linguistic testing (translation accuracy), functional testing (features work with localized content), cosmetic testing (UI displays correctly), and cultural testing (content is appropriate). Testing typically occurs after translation and before release.
Examples
- →Linguistic: Verify translation accuracy and fluency
- →Functional: Forms work with localized validation messages
- →Cosmetic: Long German text doesn't break layout
- →Cultural: Images/colors appropriate for target market
Frequently Asked Questions
How do I test without speaking the language?
Automated tests: functional tests in each locale, screenshot comparison. Cosmetic: visual inspection for obvious issues. Linguistic: requires native speakers. Partner with native testers or use professional localization QA services.
When should localization testing happen?
Stages: 1) Pseudo-localization during development (catch i18n bugs early) 2) Functional testing after translation 3) Linguistic review by native speakers 4) Regression testing before each release.