Globalization Testing Getting your software Worldready Anuj Magazine

Globalization Testing. Getting your software World-ready Anuj Magazine (Manager, Products) Citrix R&D India Pvt. Ltd.

Do you want your Software product to Interact with Global customers like any of these Images ?

What’s covered in this presentation ? • Part-1 – Overview of Software Globalization Testing • Part-2 – Some real-time myths about Globalization Testing • Part-3 – Moving Software Globalization Quality upstream

Part-1 Overview of Software Globalization

Parts of Globalization testing Internationalization (I 18 N) Globalization (G 11 N) Localization (L 10 N)

Jan Scherpenhuizen = Jan S 12 N

About I 18 N • Internationalization, or I 18 N, is the process of generalizing a product so that it can handle multiple languages and cultural conventions without the need for re-design. • Internationalization takes place at the level of program design.

Parts of I 18 N testing Unicode Clean Input / Output Process Internationalization (I 18 N) Locale Awareness Single Base Binary (SBB) Localizability Multilingual User Interface (MUI)

About L 10 N • Localization, L 10 N, involves taking a product and making it linguistically and culturally appropriate to the target locale (country/region and language) where it will be used and sold.

Parts of L 10 N testing Translation Localization (L 10 N) UI Layout

Example of part of Application not being Unicode Clean

Text Truncation

Control Overlapping

Some questions Can Localization exist successfully in a Software product without Internationalization in place ? NO Can Internationalization exist successfully in a Software product without Localization in place ? YES

Part-2 Some real time myths about Globalization Testing

Uncovering Some Myths about Globalization testing Myth# 1: Globalization Testing is primarily about testing the User Interface Myth# 2: Globalization Testing can start Only after the base product is Translated Myth# 3: A person who doesn't know French cannot test the French version of the Software Myth# 4: If a test case works fine in French language, it would work fine in German language as well. Myth# 5: The language verification of User Interface can be done by comparing the text on screen with translation outputs of any freely available Online translator

Part-3 Moving Software Globalization Quality upstream

When to start Globalization ?

Leverage Virtualized Test Environment • Localized versions of Server and Client OS • Localized Infrastructure machines (DC, Exchange, Sharepoint etc. ) • Localized keyboards • Localized 3 rd party applications to test. • Localized test data

80%

Common Globalization issues • Text Truncations • Duplicated/missing Hotkeys • Overlapping of controls • Alignment of controls • Hard coding • Character corruptions

Internationalized Automation • Eliminate the Code debt. • Apply the concepts of I 18 N Software design to Automated scripts – Minimize the UI dependence- Externalize – Data driven – Use Unicode • Make the Test scripts Language, OS, Site dependent to enable Simaltaneous running.

Pseudo Translation testing • What ? • Simulation of a localized product • Why? • Uncover G 11 N issues using EN build. • Minimize the L 10 N effort involved. • Save crucial time at later stages. • How? • Pad the English text with localized characters in the resource file

Pseudo Translation - Example Source Text = “Enable Session reliability” Pseudo translated text = “[Лаз ÜÝß Ènãblê Sèssìón rèlîàbîlîty ЙЦУ ]” Issues to look for : Hardcoding: “Enable Session reliability” Probable Truncation : “[Лаз ÜÝß Ènãblê Sèssìón rèlîàbîlîty ” Character Corruption : “[||аз ÜÝß Ènãblê Sèssìón rèlîàbîlîty |#У ]”

Pseudo Translation – In Action Pseudo Translate

Thank you Merci Danke ありがとうございました 謝謝您 감사합니다 anuj. magazine@citrix. com http: //www. citrix. com http: //anujmagazine. blogspot. com