By Himanshu Sharma on Sep 10, 2014 6:30:43 AM
“G11N” or Globalization testing is more relevant today than it was earlier and is a key aspect of software product testing. For one, to increase their market base, companies are increasingly targeting global customers tailoring features and functionality to meet user standards and formats of a particular geography. This includes preferences like platforms, browsers, language settings, currency etc. testing different combinations of the above elements becomes mission critical.
Globalization testing also means ensuring software products have relevant features and functionality to establish connect with the geographically dispersed users. It would be apt to describe Globalization testing as a process to ensure software can run independent of its geographical and cultural environment.
I asked our Associate Test Manager, “What are the key components of Globalization testing and what are the most left out aspects or minute details one has to bear in mind for globalization testing?”
Here’s what Mr. Ashwin replied:
"There are a lot of aspects that must be considered when producing a global software. Some of the aspects are as follows:
• Locale/Language/Vocabulary Sensitivity
- Date and time
- Currency handling
- Address and telephone number
• Default Size of Paper for printing
Apart from usual elements tested like platforms, cross-browser compatibility, language settings, translation capabilities etc."
I asked how was he able to minutely define such details which are often missed out in Globalization testing. He replied -
“One gets to know about various nuances of Globalization testing or for that matter other testing, when one works for a particular case and the level he drills into. In our case, we had a chance to perform globalization testing for a web-based product involved in online transaction using 25 different currencies. Also, product testing was done to ensure that mobile users in 70 countries are able to recharge their currency and perform money transfer without any problem across countries."
Mr. Ashwin also suggested some of the best practices while performing Globalization Testing as follows:
Step1: Analyze the globalization requirements in detail like the culture, standards etc.
Step 2: Ensure application seamlessly integrates with the locale/language
Step 3: Ensure application and database are able to capture and store all special characters, italics, accentuated character sets specific to the language to be supported
Step 4: Ensure there is proper formatting of dates, currencies etc. as applicable
Step 5: Ensure proper conversion rates as applicable in case of currencies
The aim of Globalization testing is to make sure acceptability, usability and reliability of a product is intact in keeping with global audiences in mind. As a service provider, more and more software testing companies are gearing to strengthen their support to meet global user experience.
Had an insightful session with Mr. Ashwin yesterday. If you have any queries or if you want to know more about how our software product testing services can help you, don’t hesitate to call us or drop a line.