ERROR: Content Element with uid "1816" and type "templavoila_pi1" has no rendering definition!
09:40 - 10:25 Uhr
Make localization software testing a bit less painful
Herb Bauer, SDL International
A long time ago in a galaxy far, far away, we used to have plenty of time to get software translations done. There were only a few major international markets and a few platforms to cover. Today, there is clearly a need for speed and agility in software development. Software must be released into many countries simultaneously, and it needs to run on an increasing number of platforms (think mobile).
In this presentation we will introduce some challenges you may face as a tester of localized software, and as a developer who is tasked with internationalization issues. Using examples of typical localization bugs, we'll show which ones are easy to avoid and which ones are harder to address.
Challenges testing software that is localized for international markets:
- Localization testing is ^%$#@! expensive and the costs go up if you get the initial development wrong
- Localization bugs that are found late are often deferred, which results in frustration and bad quality
- Unexpected localization bugs drive busy software developers crazy and keep them from working on the next great thing
- You may even miss the opportunity to enter foreign markets because of software localization problems.
Practical examples of software localization problems we've seen; where they come from; why we still have to test:
- Functional bugs caused by foreign software environments
- Translation or language-related issues
- UI layout problems caused by software translation
- Problems related to software locale and regional settings
- OS platform and hardware display issues.
Common terms you hear in our industry provide clues on how to address software localization problems found during testing:
- Plan ahead during globalization (G11n)
- Prepare your software during internationalization (I18n)
- Use tools during localization (L10n)
- Always QA and review your work during translation (T9n).
While there are no "one size fits all" solutions, there are several best practices you should implement during software development and during software localization to reduce the time and effort it takes to test and launch your software products world-wide. Here again are the central points:
- All teams required to launch a product, including localization teams and your customers, should be involved in the development process
- Internationalize your software, use common libraries and along the way, verify that your software is easy to localize
- Reduce the localization scope, reduce translation waste, carefully re-use content, validate and QA translations before going into testing
- Automate: Translation workflows, functional testing, translation quality assurance, screenshot creation, shorten bug fixing & verification.
Herb Bauer – Business Consultant, SDL International, Colorado
Herb Bauer, a native German with degrees in German and English language from the Universities of Regensburg (Germany) and Boulder (Colorado), started a successful professional translation business in 1989. As an old Bavarian, Herb was naturally drawn to the Rocky Mountains and he can typically be found either in the Test Center lab or the Colorado back country.
Herb came to SDL Colorado in July 1995, and has shaped its localization business as a project manager and testing manager. He developed the Test Center as an internal QA organization and an independent service for companies seeking outsourced localization testing. Herb built a staff of in-house test lead engineers, and a local pool of over 350 functional and linguistic software testers covering all major languages.
In 2014 Herb is using his talents as business consultant, to help SDL's clients find solutions for their international business challenges.