Localization testing verifies system works in different languages, currencies, regions.
Test scenarios:
Language:
- UI labels translated.
- Validation messages translated.
- Error messages translated.
- Date / time formats locale-aware.
- Number / currency formats locale-aware.
- Right-to-left languages (Arabic, Hebrew) — text mirrors.
Currency:
- Multi-currency conversions correct.
- Reports show correct currency.
- Currency display formats per locale.
- Historical rates correct (with ACM).
Regions:
- Time zones handled correctly.
- Business Hours per region.
- Holidays per region.
- Address formats per country.
Test approach:
- Switch user locale in test user record.
- Test in each language systematically.
- Native speakers preferred for translation quality.
- UI tests with locale parameters.
Common pitfalls:
- English-only design — labels don't fit longer translations.
- Hardcoded date formats — break in EU locale.
- No translation review — machine-translated text awkward.
- Currency calculations wrong — ACM not enabled.
Tools:
- Salesforce Translation Workbench — official translations.
- Custom Labels — for code-driven strings.
- Knowledge translation workflow — for content.
Senior insight: localization affects everything. UI, data, automation, reports.
