- log in
Software localization processes often cause bugs, like truncated text, image and text misalignment, functionality problems, garbled text, or incorrect dates and currency formats. These bugs can range from minor inconveniences to critical errors that prevent users from completing tasks. Regardless of severity, they all cause user frustration, perception of a poor quality product, or loss of reputation and consumer trust. These issues often happen because the software product wasn’t adequately prepared for the localization process. It doesn’t matter which software localization tool you use—if an error exists before you begin, it will carry through the entire process.
Internationalization testing helps catch and fix issues early, preventing them from becoming more significant problems later. And, since testing happens before software localization, it can save you significant budget because you prevent the need to repair issues in each of your localized versions.
Let’s see how it works.
Internationalization testing—sometimes called globalization testing and often abbreviated to i18n testing—verifies that the software internationalization effort has been successful and that your product can support multiple languages without impacting functionality.
Internationalization testing involves:
Thorough internationalization testing comes before the actual translation process. Its primary goal is to guarantee that your software product is adaptable and ready for multiple languages, ultimately leading to a hassle-free software localization process and a seamless user experience worldwide.
Based on our 30 years of expertise in localizing software, we’ve compiled a list of tips for effective internationalization to make the software localization process easier and enable flawless software performance across all languages and regions.
Without a plan, you can’t be sure your checks will be comprehensive
Work with software developers to create a detailed test plan that covers all critical areas such as date/time/number formatting, file/folder accessibility, data input/output, multi-byte support, and text searching/parsing. Include specific test cases for each aspect and ensure thorough coverage to catch potential issues early.
Issues are locale-specific and can vary from locale to locale
Develop test scenarios that involve the input or display of numbers, date/time, weights, currency symbols, names, titles, phone numbers, addresses, and postal codes. Include checks for locale-specific content, such as calendar formats and regional holidays. All of these should change automatically based on the locale selected. You can validate locale settings with automated scripts, but manual testing is better for catching subtle issues.
To avoid problems with file path recognition due to different characters
Create test cases with folders and files with various Latin characters, such as French, German, and Czech diacritics, and non-Latin characters, like Japanese kana or Cyrillic. Ensure that installer paths are also tested with non-default, non-ASCII characters. Automated tools can simulate different file path scenarios, but it’s best if you manually verify the results.
To avoid missing input issues because copy-pasting might not replicate real-world usage
Perform tests using direct keyboard input for non-ASCII characters, especially for languages requiring diacritics and East Asian languages using input method editors (IMEs). Create specific test cases for “dead” key combinations and IME scenarios. Update these tests to include new characters and input methods as they become relevant.
To reveal possible software localization issues (without doing the localization).
Modify translation resources to include accented characters, non-Latin scripts, special symbols, punctuation, and text expansion modifiers. Test the application with this “fake” language to uncover potential issues like text truncation, layout problems, and encoding errors. Manual testing is preferred to verify the visual and functional aspects.
To identify critical bugs early to save time and resources when you start the software localization process.
You would perform smoke tests on the pseudo-localized build with a corresponding OS test machine. Focus on identifying showstopper bugs that could halt further testing. Create a checklist of critical functionality to verify during smoke tests. Ensure all identified issues are logged and addressed before proceeding with detailed globalization testing.
To avoid usability and perception issues caused by visual and functional problems in the UI
Run visual inspections of all dialogs, dropdowns, list controls, buttons, menus, and other UI elements for each priority language. Look for issues like string truncation, misalignment, hardcoded strings, and aesthetic inconsistencies. Create a detailed report of identified problems and work with developers to resolve them.
To make sure of accuracy and relevancy by testing on target systems
Set up virtual machines (e.g., VMware, Sun Virtual Box, Microsoft Hyper-V) to simulate the target market’s fully localized operating systems. Maintain separate configurations for each locale and ensure they are up to date with the latest OS versions and language packs. In most cases, virtualization is an efficient way to manage your multilingual test environments. These virtual machines perform end-to-end tests, including installation, configuration, and functionality checks.
To avoid unexpected issues due to integrations with third-party software
Include native language versions of third-party software, such as Flash or Firefox for Japanese, in your testing plan. Ensure that your application integrates seamlessly with these software versions. Create test cases for all third-party software interactions, including installation, configuration, and functionality. Remember to update these test cases regularly to account for new versions and updates of the third-party software.
To help you address all linguistic issues and development changes before you release localized software.
Allocate sufficient time and budget to complete linguistic and localization testing in all target languages. Coordinate with translators and localization experts to address any identified issues. Create a detailed schedule that incorporates time for bug fixes and retesting.
Linguistic testing focuses on translation quality and accuracy within your software or application. Bilingual linguists and native speakers review the translations in the actual user interface to ensure contextual appropriateness, cultural relevance, and error-free language.
Localization testing ensures that all aspects of the user experience, including language, date formats, currency, and cultural references, are adapted to the target locale. The goal is to make the software or application feel natural and function correctly for users in specific regions.
Our WordsOnline platform allows you to upload,
view your quote and pay online
At Jonckers, we provide our clients with lots of options:
Many types of testing including linguistic, localization, and internationalization
Flexibility in terms of customized solutions, flexible pricing, and team models
End-to-end localization services that integrate with and impact each other
automations and an AI approach that drives speed, cost, and quality benefits
We use AI-powered tools to automate repetitive tasks like identifying text strings for translation, detecting layout issues caused by varying text lengths, identifying software strings that didn’t get translated, and performing basic consistency checks like spotting typos and formatting issues across different languages. This allows human testers to concentrate on more complex tasks that require cultural understanding and judgment, which are vital to successful software localization.
Well-internationalized software is your ticket to a smooth localization process…and your passport to user acceptance and increased sales in all your target markets. Any errors you miss now will appear in your final localized versions, and fixing them after the fact is expensive, time-consuming, and complicated. It’s essential to nail internationalization testing from the get-go.
If you’re not already thinking about internationalization testing, you’re possibly wasting money fixing bugs that could have been avoided and either delaying your entry into new markets or releasing an imperfect product. It’s time to set aside a budget and schedule and engage a partner to help you make sure your product is set up for smooth localization.
Do you want to make a plan for a smooth internationalization testing process? Contact us today. Our expert team is here to help ensure your localized software works seamlessly across all target markets.
Upload your documents to WordsOnline and pay online for a fast, simple service. 10% discount on your first order
We will help you transition to the new world of continuous localization!
