What is Globalization Testing
Definition: Globalization is related to the process of developing a software application which has the ability to run independent of its cultural and geographical environment. Globalization testing is aimed at detecting potential problems and issues in the application design that could restrain globalization. It is an important and widely-used technique to validate the usability of applications around the world with acceptance of all language inputs.
Description: A globalized software application requires a code capable of effectively handling all the international support without any functionality break that could result in either display problems or data loss. To achieve this, the code is separated from information or messages, enabling the application to be used in different languages without the need for a complete redesigning of the product.
Globalization testing is done focusing the application capabilities on the generic user base. It helps to follow a thorough and impartial approach by separating the testers from engineers and translators. Other advantages include the reduction of overall testing and support costs, cutting down testing time to boost on-time delivery, and transformation of the product into a more flexible and easily scalable avatar.
A testing strategy made by assigning the priorities to each component gives effective results. The components which should receive high priority are:
? ANSI (American National Standards Institute) format support for text data
? Extensive handling of strings (eg. components with multiple edit controls)
? Files used for data storage/exchange (eg. web based tools, Windows metafiles, and security configuration tools)
? Components which have had Globalization issues in the past
Some basic and common aspects to keep an account while testing for Globalization are:
? English vocabulary sensitivity
? Currency handling
? Regional date and time formatting
? Address and telephone number formats
? Different paper sizes for printing
Description: A globalized software application requires a code capable of effectively handling all the international support without any functionality break that could result in either display problems or data loss. To achieve this, the code is separated from information or messages, enabling the application to be used in different languages without the need for a complete redesigning of the product.
Globalization testing is done focusing the application capabilities on the generic user base. It helps to follow a thorough and impartial approach by separating the testers from engineers and translators. Other advantages include the reduction of overall testing and support costs, cutting down testing time to boost on-time delivery, and transformation of the product into a more flexible and easily scalable avatar.
A testing strategy made by assigning the priorities to each component gives effective results. The components which should receive high priority are:
? ANSI (American National Standards Institute) format support for text data
? Extensive handling of strings (eg. components with multiple edit controls)
? Files used for data storage/exchange (eg. web based tools, Windows metafiles, and security configuration tools)
? Components which have had Globalization issues in the past
Some basic and common aspects to keep an account while testing for Globalization are:
? English vocabulary sensitivity
? Currency handling
? Regional date and time formatting
? Address and telephone number formats
? Different paper sizes for printing