AEM Testing : What is Localization (i10n) and Internationalization (i18n) Testing.

Internationalization testing is a non-functional testing approach focused on ensuring that a software application can be adapted to multiple languages and regions without requiring changes to the underlying code. This process plays a crucial role in making software globally accessible and user-friendly.

Localization, internationalization, and globalization are closely related concepts that together enable a product to achieve global readiness.

---

Key Concepts

1. Localization (l10n)

Localization is the process of adapting a product or content for a specific locale, language, or market. It is often abbreviated as l10n, where “10” represents the letters between “l” and “n”. The goal of localization is to make a product feel as though it was specifically designed for a particular audience, respecting their language, culture, and regional preferences.

Key areas of localization include:

• Date and time formats
• Currency symbols and formats
• Keyboard layouts
• Sorting, aligning, and collating data
• Color schemes, icons, and symbols
• Culturally sensitive text and graphics
• Compliance with local laws and regulations

Summary: Localization ensures that an application supports a particular locale and language effectively.

---

2. Internationalization (i18n)

Internationalization is the process of designing a software application so that it can be easily adapted to different languages and regions without code changes. It is abbreviated as i18n, where “18” represents the letters between “i” and “n”.

Summary: Internationalization prepares the application to support multiple locales and languages, making future localization easier and more cost-effective.

---

3. Globalization (g11n)

Globalization refers to the broader set of processes required to make a product or service globally ready. It encompasses multilingual communication, cultural adaptation, and international trade and business processes. Abbreviated as g11n, globalization is the end goal, achieved when internationalization and localization have been successfully implemented.

Key point:

Globalization testing is effective only if internationalization testing is successful, and internationalization testing is effective only if localization is successful.

---

How They Work Together

Example: Google Search Engine

• Localization (l10n): Initially designed in English with a “look and feel” tailored to the U.S. market.
• Internationalization (i18n): Designed to support multiple languages and regions. Google is now available in 123 languages, with layouts, text, and features adapting to local requirements. For example, Google Search in India supports English and 9 widely spoken Indian languages, automatically adjusting page design based on the selected language.

Conclusion: To achieve a globally accessible and user-friendly product, internationalization testing is essential.

---

Need for Internationalization (i18n) Testing

Without proper i18n testing:

• Product quality may be compromised
• Character encoding issues may arise when switching languages
• The application may crash or behave unexpectedly
• Font styles and sizes may vary across languages, affecting UI consistency
• The product may fail to reach its intended audience

---

Internationalization Testing: Front-End Focus

Front-end i18n testing involves validating the user interface, content, and locale-specific features:

1. UI Testing: Ensure proper alignment of texts, menus, buttons, dialog boxes, images, toolbars, prompts, and alerts.
2. Content Localization Testing: Validate language-specific properties files and regional features.
3. Locale and Culture Awareness: Test date, number, currency, calendar, time, telephone, and postal code formats.
4. File Transfer and Rendering: Verify successful file transfers and correct rendering of scripts.

---

Internationalization Testing: Back-End Focus

Back-end i18n testing ensures that the server-side components support multilingual data, character encoding, and regional features. Key areas include:

• Character encoding for multiple languages
• Form data handling
• Currency and locale-specific processing
• Integration with Content Management Systems (CMS) and databases

Note: Modern databases and CMS platforms often come with built-in internationalization support.

---

Benefits of Internationalization (i18n) Testing

• Easier adaptation of software to multiple locales
• Reduced time and cost for localization
• Single internationalized source code for all product versions
• Simplified maintenance and improved quality
• Compliance with international standards
• Lower total cost of ownership

Business Impact: Proper i18n ensures that products are ready for global markets and simplifies subsequent localization efforts.

---

Internationalization in CQ5 (Adobe AEM)

CQ5 provides a translator console for managing multilingual text within the platform:

Access Translator:
http://<hostname>:<port-number>/libs/cq/i18n/translator.html
Example: http://localhost:4502/libs/cq/i18n/translator.html

Steps to Update a Key:

1. Navigate to the translator page.
2. Select the dictionary (/apps/my-project/i18n) from the drop-down.
3. Search for the key in “Filter by text” and click Filter.
4. Edit the value for the required language by double-clicking the key or the language cell.
5. Enter the new value and click OK.
6. Save changes in the toolbar.
7. Activate the updated key via the replication tree:
   • Deselect “Only Modified” and “Ignore Deactivated”.
   • Select the path for the key (e.g., /apps/my-project/i18n/en).
   • Click Activate.

Once activated, changes will be reflected on the front-end.

---

Conclusion:
Internationalization testing is a crucial step in delivering globally-ready software. It ensures that applications can seamlessly support multiple languages, cultures, and regions, reducing localization effort and improving user experience.

Happy Testing!