Load every locale directly
Test each supported localized URL in a fresh browser session, not only by clicking a language switcher. Direct navigation can expose missing route configuration, incorrect fallback behavior, or assets that only load from the default path.
Check text expansion in real layouts
Translations often differ in length from the source text. Inspect navigation, buttons, forms, dialogs, and small screens for wrapping or clipped content. Include long labels and error messages because they frequently reveal layout assumptions.
Verify locale-specific formatting
Language selection is only part of localization. Check how dates, numbers, currencies, and units are formatted for the chosen locale where the application displays them. Make the intended locale behavior explicit and avoid relying on a browser default when the product needs a consistent result.
Look for untranslated and mixed-language states
Review menus, validation errors, empty states, loading indicators, and less common routes. A page can appear translated while a shared component or an error message remains in the source language. Test workflows that cross multiple routes and components.
Keep translation review in the release checklist
Before release, note which locales were tested, which screens were checked, and who reviewed the wording. Angular’s i18n guide explains the framework localization workflow; the Internationalization demo provides a small example to explore alongside the official documentation.
References & further reading
References are provided for context. Links to these resources do not imply endorsement or guarantee search rankings.