globalization testing - getting your software world-ready

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

Globalization(G11N)

Parts of Globalization testing

Internationalization (I18N)

Localization (L10N)

Jan Scherpenhuizen = Jan S12N

About I18N

• Internationalization, or I18N, 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.

Internationalization

(I18N)

Locale Awareness

Localizability

Multilingual User Interface (MUI)

Parts of I18N testing

Unicode Clean

Input / Output Process

Single Base Binary (SBB)

About L10N

• Localization, L10N, 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.

Localization(L10N)

Parts of L10N testing

Translation

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 3rd 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 I18N 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

• How?

• Pad the English text with localized characters in the resource file

• Why?

• Uncover G11N issues using EN build.

• Minimize the L10N effort involved.

• Save crucial time at later stages.

Pseudo Translation - Example

Source Text = “Enable Session reliability”

Issues to look for :

Pseudo translated text = “[Лаз ÜÝß Ènãblê Sèssìón rèlîàbîlîty ЙЦУ ]”

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 youMerciDanke

ありがとうございました謝謝您감사합니다

anuj.magazine@citrix.comhttp://www.citrix.com

http://anujmagazine.blogspot.com