PowerPoint Slides

1,946 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,946
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
38
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • In the globalization process, the more effort you put into the I18N phase, the less on-going effort is needed in subsequent localization phases. If a product will be localized into more than one language, I18N sufficiency testing is a key component to keeping the schedule and budget on target. The main goal of I18N testing is to find show stopping problems before they are replicated into various languages.
  • This allows you to filter out English based bugs versus locale specific bugs.
  • Non English testing- Most commonly used are German, Japanese or Chinese test environemnt Using Online Help and User Guides to develop test cases will verify that all functionality is properly tested
  • International Setup Testing          Make sure the installation program packed by InstallShield or the other software is run properly in the target OS. Some common issues including the following: -          The setup UI is not localized in local language. -          The target OS has some localized folder names so the setup can cause some issue, etc. -          The default installation path is hard-coded to C:. The Japanese NEC PC 98 series computers have floating drive architecture and the default installation drive may not be the C: drive.          Under localized Windows, the installation path should be able to support directory name with extended ASCII characters or multi-byte characters. Testing International Character/Text Support          Extended and multi-byte characters display properly in all edit fields.          Edit fields for passwords cannot allow multi-byte characters and the IME should be disabled.          Edit fields for passwords should not allow extended ASCII characters, or should be tested to ensure input of extended characters using dead-keys is also supported.          E-Mail address fields should not allow extended or multi-byte characters.          URL addresses support extended ASCII and multi-byte characters for intranet applications.          Cut, copy, paste, and drag-and-drop of extended ASCII and multi-byte characters.          Buffer sizes correctly support the required length for multi-byte characters and extended ASCII character input.          Word wrapping does not corrupt a multi-byte character.          Backspacing must delete an entire multi-byte character.          The cursor cannot be placed in the middle of a multi-byte character.          Connection to a shared folder or resource named with extended ASCII or multi-byte characters.          Euro Symbol The Euro Currency symbol € (alt+0128) must be tested in all locales with the proper Euro symbol support installed if not already installed by the system.          Extended Characters & Unicode All test scenario involving text data string manipulation, input, and display should be performed with extended character set between code point 128 - 255 in each supported Win9x locale. On platforms offering Unicode support such as NT4 and Windows2000 we should verify that unicode characters can be accepted and displayed correctly.          Double Byte Characters Double Byte Character Set should be verified on each supported Far East locale, with special emphasis on boundary cases and known problematic character code points, including double byte space characters and double byte numerals, as well as various types of characters in the target character set as appropriate. Testing should verify that query input field properly interfaces with Input Method Editor natively shipped with supported platform(s) as applicable for Far East languages. Testing should also include sending/receiving strings mixed single byte and double byte characters.          International sufficiency testing must also ensure proper support and handling of files and objects named with extended ASCII and multi-byte characters. The following general test cases should be verified: -          Files can be saved with extended ASCII and multi-byte character names -          Files named with extended ASCII and multi-byte characters can be opened or deleted -          Files or OLE objects named with extended and multi-byte characters can be cut, copied, pasted, and embedded in documents or other containers -          Files named with and containing extended ASCII and multi-byte characters can be printed
  • Testing Internationally Local Conventions          Time Setting          Date Settings          Currency Settings          Number Settings          Sort Order/Collation          Address          Name          Inter-operation: For example, if it is a web-based application, perform testing on the test cases when the client/browser's locale and the server side locale are different. Do the date/time, numerical value, etc. are presented according to locale conventions of the client/browser? C.2.4 Other consideration          Does any user interface violate Internationalization design rules, such as icon, GUI, locale sensitive fields, etc.? Does any user interface may not be accepted by some country or region due to political or legal reason?
  • Non extracted strings (Hard coded strings): -        Non-extracted strings are text in a software product that has not been given a resource ID, when text was extracted into resource files by the developer. -        Therefore strings that have not been extracted into resource files will show up in English in a software product and are therefore not localized.   Truncations: -        European languages usually have increased text size than in English. -        Asian languages are usually larger because of double bite characters.   Concatenated Strings: -        This is a string that has two strings in one (i.e. two sentences in one line) -        It is important to avoid this set of strings, as it can be difficult during localization. You should always avoid concatenated strings and rather separate strings and give them their own string ID Uses a delimiter at the beginning and the end of text to test the truncation and proper positioning of the text in the UI.
  •   a.      English text is still readable even though it contains accented characters   Issues: b.      Text wraps around “Permission” and needs to be resized c.      The “Check” button is still in English and was not extracted into a resource file due to hard coded issues
  • PowerPoint Slides

    1. 1. Internationalization (I18N) Sufficiency Testing Presented to Seattle Area Software Quality Assurance Group June 19 , 2003
    2. 2. What We Will Cover <ul><li>Globalization and Its Components </li></ul><ul><li>Pre-Testing Checks </li></ul><ul><li>Test Environments </li></ul><ul><li>Test Checklists </li></ul><ul><li>Test Execution </li></ul><ul><li>Pseudo Localization Testing </li></ul>SASQAG: Internationalization Testing
    3. 3. Globalization <ul><li>Globalization </li></ul><ul><ul><li>The process of designing, developing, and engineering products that can be launched worldwide </li></ul></ul><ul><ul><li>Two major Components – Internationalization & Localization </li></ul></ul><ul><ul><ul><li>Internationalization (I18N) </li></ul></ul></ul><ul><ul><ul><ul><li>Designing/developing software so it can be adapted to various locales and regions </li></ul></ul></ul></ul><ul><ul><ul><li>Localization (L10N) </li></ul></ul></ul><ul><ul><ul><ul><li>Process of adapting software by translating text and adding locale –specific components </li></ul></ul></ul></ul><ul><li>I18N Sufficiency Testing </li></ul><ul><ul><li>Ensures software has been properly internationalized according to design rules and is READY to be localized. </li></ul></ul>SASQAG: Internationalization Testing
    4. 4. Benefits of I18N Testing <ul><li>The main goal of I18N testing is to find potentially show stopping software problems before the application is translated and localized into various languages </li></ul><ul><li>I18N sufficiency testing must begin as early in the testing cycle as possible </li></ul><ul><li>I18N sufficiency testing does not require an in-depth knowledge of many locale specific issues, a fully localized environment, or native linguistic skills. </li></ul>SASQAG: Internationalization Testing
    5. 5. Pre-Testing Checklist <ul><li>Step 1: Review developmental specs to determine whether they accounted for international considerations </li></ul><ul><ul><li>Code review </li></ul></ul><ul><ul><li>English language compatibility? </li></ul></ul><ul><ul><li>DB or Unicode enabled from the ground up? </li></ul></ul><ul><li>Product Rules </li></ul><ul><ul><li>Menu and dialogue box designs; Did they leave room for text expansion? </li></ul></ul><ul><li>Source Code Control Rules </li></ul><ul><ul><li>All editions are using Unicode and/or DBCS based on a single executable </li></ul></ul><ul><li>Coding Conventions </li></ul><ul><ul><li>Code should NOT assume that characters are 8 or 16 bit </li></ul></ul>SASQAG: Internationalization Testing
    6. 6. Setting Up Your Test Environment <ul><li>Step 1: Prepare the required SW and HW </li></ul><ul><ul><li>Localized Operating Systems </li></ul></ul><ul><ul><li>Localized HW </li></ul></ul><ul><ul><li>Localized third party SW utilized by the product you are testing </li></ul></ul><ul><ul><li>Verify that the network/HW peripherals that are needed to run the product are capable of running in a multi-locale environment </li></ul></ul><ul><li>Step 2: Install the Environment </li></ul><ul><li>Step 3: Configure the Environment </li></ul><ul><ul><li>Setting up machines for multi-boot </li></ul></ul><ul><ul><li>Using test bed images </li></ul></ul><ul><ul><li>Managing the test bed matrix </li></ul></ul><ul><ul><li>Maintain an English Reference Environment (Whenever Possible) </li></ul></ul>SASQAG: Internationalization Testing
    7. 7. Setting up Your Test Environment Continued <ul><li>Step 4: Define the Configuration Management Process </li></ul><ul><ul><li>Document the configuration of each machine in the environment to ensure that you are using the right products to test your application </li></ul></ul><ul><ul><li>Detail the process for saving and restoring the multi-boot and test bed imagining </li></ul></ul>SASQAG: Internationalization Testing
    8. 8. Test Checklist <ul><li>Items needed to Create the I18N Test Plan </li></ul><ul><ul><li>Installation/Configuration Guides </li></ul></ul><ul><ul><li>English test plan and test cases </li></ul></ul><ul><ul><li>Online Help/User Guides </li></ul></ul><ul><li>During Test Plan Creation ensure that you: </li></ul><ul><ul><li>Check all areas in which a user can enter, modify, print, edit, or copy data </li></ul></ul><ul><ul><li>Create test cases to verify that target language characters can be correctly entered and displayed </li></ul></ul><ul><ul><li>Build in non English data and environment testing </li></ul></ul><ul><ul><li>Verify that a user can read/write to the target platform file system </li></ul></ul><ul><li>Set Up a Testing Priority Level </li></ul><ul><ul><li>Types of testing (I18N, LVT, etc.) </li></ul></ul><ul><ul><li>Categories (documentation, help files, screen shots, etc.) </li></ul></ul><ul><ul><li>Locale Priority ( i.e Chinese then French) </li></ul></ul>SASQAG: Internationalization Testing
    9. 9. Test Checklist Part 2 <ul><li>Testing Team and Development Team Interaction </li></ul><ul><ul><li>It is important for Test Engineers to understand the scope of any code changes made by the development team </li></ul></ul><ul><ul><ul><li>For example, areas of the code that are unchanged during I18N should have less emphasis during the test phase </li></ul></ul></ul>SASQAG: Internationalization Testing
    10. 10. Test Execution <ul><li>1. International Setup Testing </li></ul><ul><ul><li>Installer Issues </li></ul></ul><ul><li>2. Testing International Character/Text Support </li></ul><ul><ul><li>Edit fields can display extended/multi-byte characters </li></ul></ul><ul><ul><li>Cut/Copy/Paste/Drag extended character testing </li></ul></ul><ul><ul><li>Euro Symbol Testing </li></ul></ul><ul><ul><li>Unicode Character testing </li></ul></ul><ul><ul><li>IME Testing </li></ul></ul><ul><li>3. Files can be saved with extended ASCII and multi-byte character names </li></ul><ul><li>4. Files named with extended ASCII and multi-byte characters can be opened or deleted </li></ul>SASQAG: Internationalization Testing
    11. 11. Test Execution Part 2 <ul><li>5. Files or OLE objects named with extended and multi-byte characters can be cut, copied, pasted, and embedded in documents or other containers </li></ul><ul><li>6. Files named with and containing extended ASCII and multi-byte characters can be printed </li></ul><ul><li>7. Testing Internationally Local Conventions </li></ul><ul><ul><li>Time/date settings </li></ul></ul><ul><ul><li>Currency testing </li></ul></ul><ul><ul><li>Sort order/Collation </li></ul></ul><ul><ul><li>Address/name fields </li></ul></ul><ul><li>8. Other considerations </li></ul><ul><ul><li>Geopolitical issues/locale-sensitive issues </li></ul></ul>SASQAG: Internationalization Testing
    12. 12. Pseudo Localization Testing <ul><li>Pseudo Localization is a process to ensure that three main issues are covered within a software product UI. </li></ul><ul><ul><li>Non Extracted Strings (hard coded strings) </li></ul></ul><ul><ul><li>Truncations </li></ul></ul><ul><ul><li>Concatenated Strings </li></ul></ul><ul><li>Pseudo-localization simulates the process of localizing products, by completing many of the localization tasks without actually using translation. </li></ul><ul><li>Also called Localizability Process </li></ul>SASQAG: Internationalization Testing
    13. 13. Pseudo Loc FAQs <ul><li>When do you perform Pseudo Loc? </li></ul><ul><ul><li>During core code development prior to localization </li></ul></ul><ul><ul><li>Typically multiple cycles </li></ul></ul><ul><li>How do you perform Pseudo Loc? </li></ul><ul><ul><li>Extract the strings into a resource file </li></ul></ul><ul><ul><li>Add extended characters to simulate European and Asian languages </li></ul></ul>SASQAG: Internationalization Testing
    14. 14. An Example of Pseudo Localization SASQAG: Internationalization Testing
    15. 15. Questions and Answers <ul><li>Conclusions </li></ul><ul><li>Questions Anyone? </li></ul><ul><ul><li>I may have an answer </li></ul></ul><ul><ul><li>I may also have a heart attack </li></ul></ul>SASQAG: Internationalization Testing
    16. 16. Thank You and Resources <ul><li>Thanks SASQAG for asking me to come here tonight </li></ul><ul><li>White Papers available on our website, www.symbio-group.com </li></ul><ul><li>If you have additional questions, I can be reached at [email_address] </li></ul>SASQAG: Internationalization Testing

    ×