Testing for world readiness
The goal of ensuring world-readiness has a wider scope and requires more fore-thought than merely testing localized applications. It must start early on by determining the necessary criteria for globalization and hence world-readiness.
Single code-base design, unified data-processing algorithms, and elimination of functionality problems due to localization are some of the benefits of software globalization. These benefits will reduce redundancy in test runs on localized products and make simultaneous release possible.
The first step to test the world-readiness of a product is to verify that its functionality is globalized. Rather than testing for globalization of every single system component, by globalizing the test you check for world-readiness at the same time you check the general functionality of the product.
The purpose of localizability testing is to verify that the user interface of the program being tested can be easily translated to any target language without re-engineering or making code modifications. Since localizability bugs have to be fixed in the core application code, they must be discovered early.
Localization testing checks how well the build has been translated into a particular target language. This test is based on the results of globalized testing where the functional support for that particular locale has already been verified.
Using automated test tools is an effective way to verify the functionality of localized products or to test a product's globalization. Automation makes it easier to deal with the high volume of test cases and allows you to efficiently track the results of the globalized test. Restoring the locale settings or test input that brought about a failure in a program also becomes easier.
The sample test items are broken up into basic areas of functionality and are accompanied by details on how these areas can be verified. The test cases describe potential problems associated with certain areas and when the test is applicable.