Enterprise Library Test Guide - Willy .Net
Enterprise Library Test Guide - Willy .Net
Enterprise Library Test Guide - Willy .Net
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
164<br />
<strong>Enterprise</strong> <strong>Library</strong> <strong>Test</strong> <strong>Guide</strong><br />
To use pseudo-localization, alter the application block’s localizable resources in the<br />
following ways.<br />
●<br />
●<br />
●<br />
●<br />
Replace English text with text that contains non-English characters.<br />
Add extra characters to the resource strings. This ensures that the application<br />
block functions even if the translated text is longer than the English text.<br />
Add markers before and after the non-English strings. This test ensures that the<br />
application block displays the complete string and does not lose data. For example,<br />
you can enclose all strings within "[]" so that you can see where each string<br />
begins and ends.<br />
Use multi-lingual Unicode for all the substitutions and additions. This will help<br />
you find places where the application block uses ANSI functions to process or<br />
display text.<br />
Creating the <strong>Test</strong> Environment<br />
When you create a test environment, it is important to select the correct operating<br />
system. Windows XP is often a good choice for globalization testing because it supports<br />
a broad range of cultures. This means you can simulate many different regions<br />
on a single computer. Use the local build of Windows XP with a language group<br />
installed. For example, if you use the U.S. build of Windows XP, you could install the<br />
East Asian language group. Because German is installed by default, this combination<br />
gives you good test coverage without imposing requirements on the testers’ language<br />
skills.<br />
Another option is to use the local build of the target operating system. If the applications<br />
are meant for specific regions, the versions of the operating system that are<br />
tailored for these regions are the obvious choices for the builds. If the target operating<br />
system is Windows 2000 or Windows XP, you can use one language for the<br />
system UI and another for the actual application. By using this configuration, you<br />
can see how the application interacts with a localized system, where the names of the<br />
system folders, built-in accounts, fonts, and other system objects might be different<br />
from how they are represented in an English or Multilanguage User Interface (MUI)<br />
system. You can choose to use whatever language for the system UI that the testers<br />
understand.<br />
The <strong>Enterprise</strong> <strong>Library</strong> application blocks do not have specific requirements for<br />
the cultures that they must support. To see if the application blocks could support<br />
diverse cultures, they were tested with a minimum of two language groups that belonged<br />
to linguistically unrelated regions, such as Japan and Germany.