How is internationalization testing conducted in an application?

Internationalization (i18n) testing verifies that the application's architecture supports localization. This includes checking:

• Absence of hardcoded strings: All static text elements should be extracted from external resources.
• Correct display of characters: Support for various alphabets, special characters, and diacritics.
• Support for data formats: Proper display of dates, times, numbers, and currencies in different regional formats.
• No dependency on locale in code: The application's logic should not depend on a specific language or region.
• Correct handling of encodings: Use of appropriate encoding, such as UTF-8.
• UI/UX flexibility: Interface design should accommodate changes in text length, writing direction (LTR/RTL), and font size.

Testing methods:

1. Pseudo-localization: Using artificially generated "language" to identify issues with string length, character support, and hardcoded text early in development.
2. Testing on various locales: Installing and running the application in different supported operating system locales or within the app.
3. Formatting verification: Testing the display of dates, times, numbers, and currencies using regional settings.
4. UI validation: Ensuring all interface elements display correctly, without text truncation or element overlap.
5. Sorting testing: Verifying correct data sorting according to the rules of the selected locale.
6. Search testing: Ensuring search functions correctly considering locale specifics (e.g., ignoring accents).
7. Input/output data testing: Checking correct processing and display of data entered in various locales, as well as data exported by the app.

Tools may include:

• Tools for creating pseudo-localized resources.
• Frameworks for automated UI testing (Selenium, Appium), adapted for checking text and interface elements in different locales.
• Browser plugins or tools for changing locale in OS/browser.

i18n testing is conducted during development and testing phases, often alongside functional testing, before the localization (l10n) stage.