Multilingual Testing

Hi guys,

According to experience of multilingual website testing, I try to write some checklist for it, hope it will help you while you are going to test such application. It was great experience to test

Multilingual Testing Checklist

• To check correct translation, using help of web automated translation like google translation.
• Get really comfortable with the application - Since you might not know the languages supported by the web site, it is always a good idea for you to be very conversant with the functionality of the web site. Execute the test cases in the English version of the site a number of times. This will help you find your way easily within the other language version. Otherwise, you might have to keep the English version of the site open in another browser in order to figure out how to proceed in the other language version (and this could slow you down).
• Start with testing the labels: You could start testing the other language version of the web site by first looking at all the labels. Labels are the more static items in the web site. English labels are usually short and translated labels tend to expand. It is important to spot any issues related to label truncation, overlay on/ under other controls, incorrect word wrapping etc. It is even more important to compare the labels with their translations in the other language.
• Move on to the other controls: Next, you could move on to checking the other controls for correct translations and any user interface issues. It is important that the web site provides correct error messages in the other language. The test should include generating all the error messages. Usually for any text that is not translated, three possibilities exist. The text will be missing or its English equivalent will be present or you will see junk characters in its place.
• Do test the data: Data in different languages can be easily represented in this format.
•  Make sure to check the input data. It should be possible to enter data in the other language in the web site. The data displayed by the web site should be correct. The output data should be compared with its translation
• Be aware of cultural issues: A challenge in testing multi-lingual web sites is that each language might be meant for users from a particular culture. Many things such as preferred (and not preferred) colors, text direction (this can be left to right, right to left or top to bottom), format of salutations and addresses, measures, currency etc. are different in different cultures. Not only should the other language version of the web site provide correct translations, other elements of the user interface e.g. text direction, currency symbol, date format etc. should also be correct. As you might have gathered from the tips given above, using the correct test environment and acquiring correct translations is critical in performing a successful test of other language versions of a web site.
• Date format according to culture, For ex., in English culture date display in mm/dd/yyyy format, while in Italian culture it should display in dd/mm/yyyy format.
• Currency should display according to culture. For ex. In English culture amount display as 100.00 $, while in Italian culture it should display as 100,00 $ .
• Label alignment , text direction, text alignment should be proper
• When page is redirect from one page to other, at that time, currency format should handle proper
• All UI element display in respective language, like window title, page title, tool tip, all labels on page, error messages, bread crums, image alter text etc
• Check the database value of all the inputs with respective tables
• Check database related testing for it
• If payment gateway is there then, when it redirect from the payment gateway page to application, then verify currency format etc

• Localization Testing: Localization translates the product UI and occasionally changes some initial settings to make it suitable for another region. Localization testing checks the quality of a product's localization for a particular target culture/locale. This test is based on the results of globalization testing, which verifies the functional support for that particular culture/locale. Localization testing can be executed only on the localized version of a product. Localizability testing does not test for localization quality. Localization testing include:
• Basic functionality tests
• Setup and upgrade tests run in the localized environment
• Plan application and hardware compatibility tests according to the product's target region

The localization testing of the user interface and linguistics should cover items such as:

• Validation of all application resources
• Verification of linguistic accuracy and resource attributes
• Typographical errors
• Consistency checking of printed documentation, online help, messages, interface resources, command-key sequences, etc.
• Confirmation of adherence to system, input, and display environment standards
• User interface usability
• Assessment of cultural appropriateness
• Checking for politically sensitive content

When shipping a localized product, ensure that localized documentation (manuals, online help, context help, etc.) is included. Items to check include:

• The quality of the translation
• The completeness of the translation
• Terminology is used consistently in all documents and application UI

What we need to consider in Localization Testing?

Things that are often altered during localization, such as the User Interface and content files.

• Keyboards
• Text Filters
• Hot keys
• Spelling Rules
• Sorting Rules
• Upper and Lower case conversions
• Printers
• Size of Papers
• Mouse
• Date formats
• Rulers and Measurements
• Memory Availability
• Voice User Interface language/accent
• Video Content