Localization testing is crucial throughout the entire globalization process when adapting software and websites for new markets.
Subscribe to our blog
If you haven’t thought about it, consider that localization testing is crucial throughout the entire globalization process. You wouldn’t want to ship a localized product to China, for instance, with unreadable, corrupted text that runs off the page.
Adequate testing ensures that you deliver a high-quality product, catching—and correcting—any bugs that come up in the localization process before it’s released. It saves you time and money, too. After all, finding these errors post-release can mean costly rework and having to address them multiple times (for each target language).
Let’s take a look at three localization testing methods so you can avoid any and all setbacks.
1. Internationalization readiness testing
How primed is your software or website for localization? That’s what internationalization readiness testing can tell us. Think of it as taking preventative measures to ensure localization will go smoothly.
This phase of testing can show us how well your product functions in an international environment—including how it interacts with native language operating systems and third-party applications. We assess how your product can handle different characters and writing systems (for example, bi-directional scripts).
We’ll also ensure your product can support a multilingual user interface and locale-specific formats for time and dates, currency symbols, phone numbers, addresses, zip codes and more.
We then supplement this with pseudo-localization, where we “fake” how your strings will look in each target language, which helps us identify hard-coded strings and potential over-translation issues (for example, if a user interface string is also referenced within the code, which would impair functionality). It will also highlight any probable design issues with how the product can accommodate a translated interface.
In short, benefits of internationalization testing include:
- Increased product quality—if built to support internationalization
- International visibility for the product
- Wider, international audience reach
- Global product release with lesser expense comparatively
2. Localization testing
While internationalization readiness testing occurs before translation, the next two testing phases take place after a significant portion of translation work has been completed. The purpose of localization testing is to ensure that bugs weren’t introduced during the translation process, that the translated content displays correctly, and that the localized product functions as expected for the target market. Testing websites to ensure adaptability to a particular locale and culture is also crucial to suggest its superiority in the target market.
Here are some areas we examine during this test:
- All localization resources are translated correctly
- The generated build includes all necessary files
- Functionality in localized version(s) is consistent to the source product
- The localized screen has the same number and type of elements as that of the source product
- All locale-specific characters appear correctly
- No words run over buttons or get cut off on the page
Of course, this is just a mere glimpse into the many elements we look at during this phase. But basically, we want to be sure everything appears correctly and functions how it should after translation happens.
Localization testing also must take into account differences in culture, such as:
- Local holidays
- Personal name and title conventions
- Comprehensibility and cultural appropriateness of images and color symbolism (take a look at an earlier post on the topic of “high- and low-context cultures” for more on this)
- Ethnicity, clothing, and socioeconomic status of people and architecture of locations pictured
- Local customs and conventions, such as social taboos, popular local religions, or superstitions such as blood types in Japanese culture vs. astrological sign in other cultures
And of course, different countries have different legal requirements that must be considered. Regulatory compliance may require customization for a particular jurisdiction, or change to the product altogether. Examples might include privacy law compliance, or consumer labeling requirements, or even additional disclaimers on packaging. This process will ensure you don’t end up dealing with a legal mess post-launch.
3. In-context review
An in-context review puts the final polish on your website or software. This test has much more to do with translation quality than product functionality. With this form of localization testing, a qualified linguist reviews the translations in the actual product build (which is extremely valuable). Why is this so crucial?
You see, a linguist can view the strings in the environment where they naturally reside instead of in an isolated source text file or a translation tool. This allows the reviewer to get a better understanding of the context and flow of the product and gives greater clarity into which translation is best to use—which means better translation quality.
Let’s look at an example. The word “home” has many meaning possibilities. It can refer to an action button that helps you return to the homepage of a website. It can also be a noun indicating that you should enter your home address on a contact form. Seeing the translation in context, therefore, clears up any ambiguity around which translation is correct.
The in-context review step—and even the testing—is typically done by the native speaker of that specific language. This means you’ll have separate linguists for these steps in the globalization process.
During this step, the linguist will also give the final sign off on translation quality, making sure that the copy fits the locale as well as matches your company’s branding preferences.
Want to learn more?
Localization testing is just one of the ways to reduce the cost and minimize the number of potential pitfalls on the software and website localization road. A test automation approach should be applied in testing websites to optimize costs and reduce testing time.
Of course, you can always lean on our expert teams. Contact us to see how we can help you with your next project.
If you’ve localized your website or software, what tests did you use to make sure your end product was high quality for each locale?
➡ Read this article in French
➡ Read this article in German
About the author
Gretchen Sampair is a Digital Communications Specialist at AMPLEXOR International and based in Wisconsin. Gretchen joined AMPLEXOR in July 2017 and specializes in marketing content for global content solutions.