What is Internationalization & Localization Testing?
0 likes655 views
The document outlines the importance of internationalization (i18n) and localization (l10n) testing for global products, emphasizing the need for products to be accessible in different languages and regional standards. It covers the testing approaches, including enablement testing, localizability testing, and localization testing, detailing their processes and purposes. Additionally, it highlights the challenges and best practices for localization testing to ensure functionality and linguistic accuracy across various locales.
What is Internationalization & Localization Testing?
- 2. Agenda ● Need and Purpose ● Definitions- G11N, I18N and L10N ● Unicode ● G11N Testing Approach for Global Products ● Internationalization Testing- -Enablement Testing -Localizability Testing ● Localization testing -Functional Testing -Linguistic Testing Copyright © by QAInfoTech. All rights reserved.
- 3. Need & Purpose ● English is NOT spoken by 2/3 of the world's population ● It is very difficult to survive in the current world if you are selling your product in only one country or geological region. ● Even if you are selling your product all over the world, but it is not available in the regional language, you are likely to face certain obstructions. ● Products developed in one location are used all over the world with different languages and regional standards. This increases the need to develop a globalized product and test it in different languages with varied regional standards. Copyright © by QAInfoTech. All rights reserved.
- 4. G11N, I18N and L10N Copyright © by QAInfoTech. All rights reserved.
- 5. Copyright © by QAInfoTech. All rights reserved.
- 6. Unicode Unicode is the worldwide standard which assigns a unique number to each and every character. (S (Image Source: https://upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Unicode_logo.svg/1200px-Unicode_logo.svg.png) The Unicode Standard has been adopted by many leaders in the industry such as Apple, HP, IBM, JustSystems, Microsoft, Oracle, Unisys and many more. Copyright © by QAInfoTech. All rights reserved.
- 7. G11N Testing Approach for Global Products Copyright © by QAInfoTech. All rights reserved.
- 8. Internationalization Testing Internationalization testing can be further categorized into: 1) Enablement Testing:- Enablement is an engineering exercise guaranteeing that the data input (keyboard,voice,paste), output (display,print,copy) and manipulation in an application can happen for all supported languages/scripts without corruption. The various scenarios for such a type of testing are- ● Graphical User Interface Scenarios ● Date and Time Settings Scenarios ● Search and Sort Scenarios ● Data Import and Export Scenarios ● Number Format Scenarios ● Printing Scenarios ● Unit of Measurement Scenarios Copyright © by QAInfoTech. All rights reserved.
- 9. Enablement Issues ● The appearance of default glyphs such as boxes, vertical bars, or tildes () indicate that the selected font cannot display some of the characters. Copyright © by QAInfoTech. All rights reserved.
- 10. ● Appearance of question marks instead of the text inserted, indicates the problem in Unicode-to-code-page conversion. Copyright © by QAInfoTech. All rights reserved.
- 11. ● Junk or random characters appearing instead of the text inserted, indicates that the application is using the wrong code page. Copyright © by QAInfoTech. All rights reserved.
- 12. Internationalization Testing 2) Localizability Testing or Pseudo Localization Testing:- Localizability testing is performed to ensure that there is no hardcoded string in the application. It helps in identifying the strings in UI which have not been externalized for localization (i.e. hard-coded strings). Purpose Of Localizability Testing:- ● Finding the hard coded strings in the application UI ● Finding functional issues a) Application is installable b) Acceptance/sanity test cases pass seamlessly ● Finding UI issues Copyright © by QAInfoTech. All rights reserved.
- 13. How is Localizability Testing done? ● Localizability testing is done through the pseudo-localized builds (commonly known as mock builds). ● The process of creating pseudo-localized builds starts from manipulating the linguistic resources of the application to reflect language/locale-specifics, followed by a build and then the runtime testing. The steps of creating pseudo-localized builds are: ● Externalization of strings into a resource file ● Pseudo-translation ● Pseudo-localized builds Localizability testing should start a week or two prior to sending the first glossary kit (Gkit) to the translators or linguistic vendors. Copyright © by QAInfoTech. All rights reserved.
- 14. Localization Testing Localization testing can be further categorized into: Functional Testing :- Functional testing is performed to make sure that all features of an application are working seamlessly on the localized operating system. Linguistic Testing :- Linguistic testing is performed to make sure that there aren’t any translation or grammatical mistakes in the content of an application. UI issues are also tested such as truncation, font etc. Localization testing becomes a collaborative effort of functional QA engineers and linguistic experts wherein both work simultaneously to ensure that functionality and the linguistic usage is accurate. Copyright © by QAInfoTech. All rights reserved.
- 15. Difference between Locales Copyright © by QAInfoTech. All rights reserved.
- 16. Localization Testing Challenges ➔ Localization expert engineers ➔ Domain expertise ➔ Hardware and software management ➔ Cumbersome linguistic process ➔ Coverage over all types of testing Copyright © by QAInfoTech. All rights reserved.
- 17. Localization Testing Best Practices ● All functionalities/features work fine on the localized version of an application ● Linguistic sorting, file/folder accessibility, text searching, data input/output is accurate ● 2 & 4-byte character support ● Date/time formats, calendar, currency, weights or measures are supported ● Always use localized username and password while testing. ● Functional testing should always be performed on native OS and use of MUI/MLP’s should be avoided ● Use of language translators ● Replicate behaviour on English versions of an application ● Use of localized keyboards ● Check the compatibility with supported localized browsers ● Verify that cut/copy/paste between applications work seamlessly Copyright © by QAInfoTech. All rights reserved.