var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-333696-1']); _gaq.push(['_trackPageview']); _gaq.push(['_trackPageLoadTime']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })();
  • 2007年04月19日

    Execute appropriately in a multilingual environment

    分类:

    Req 1.5  Execute appropriately in a multilingual environment

    Customer Benefits

    Goes here…

    Test Objectives

    Two aspects of multi-lingual environment support are required for certification:

    ·         Perform all primary functionality on systems localized to the language the application is advertised as supporting.

    To qualify as a Unicode Application, the application must also support all of the recommendations to work in a Configurable Multilingual Environment.

    ·         Install and run when the user name contains one or more characters from a script of  the language  as the application is advertised as supporting 

    To qualify as a Unicode Application, the application must also fully support paths, URLs, and printer names containing characters from any language, even when the locale settings do not match. 

    Tools

    String Generator

     

    How to generate Unicode strings:

    n  Use “String Generator” tool located at http://www.microsoft.com/globaldev/tools/strgen.mspx;

    n  Localization glossaries for already released products: http://www.microsoft.com/globaldev/tools/MILSGlossary.mspx.

    Implementing the Tests

    Setup for multi-lingual testing:

     

    1)    Install a language-specific SKU of Windows Server (Longhorn), and for Client components, Windows Vista.

     

    Or, alternately,

     

    2)    Before installing the application onto the computer, install supplemental language support as follows: Obtain a Language (MUI) Pack for appropriate language/platform to your locale machine from MSDN subscription and insert appropriate Language Pack installation CD into your disk drive. Go to Control Panel, select Regional and Language Options, click the Keyboards and Languages tab and click the Install/uninstall languages… button under Display language. Windows titled “Install or Uninstall Display Languages” shows up. Click the Browse folder… button to locate the language file copied, follow steps to finish the language installation.

    NOTE: Approximately 200+ MB additional hard disk space on your Windows drive is required for every language installed. Note that Language (MUI) Packs may not be available as yet for download from Microsoft for Windows Server (Longhorn).

    Add a user with a name in a script for a non-Latin language such as Japanese. From the Start menu, select Administrative Tools, and then select Computer Management. Go to Local Users and Groups/Users and create a new user. Here is a sample user name which you could cut and paste into the new user dialog “裹ソポァゼゾタボマ”. If the application is being tested for full Unicode compliance, include characters from a mix of language scripts in the user name.

     

    If not testing for full Unicode compliance, you will want to make the test easier to pass by making both regional settings and the user name script to match the application language. Open Control Panel and select Regional and Language Options, select the Formats tab, and change the Current format: setting to match the script for the user you just created, which also matches the application language. Select the Administrative tab and change the language for non-Unicode programs to the same language by clicking the Change system locale… button, and then Click the Copy to reserved accounts… button to apply the setting to default user account and system account if needed.

     

    Log on with this user name by manually entering the characters in the Windows logon dialog box, or set up the system to automatically log in with the user name. To do this, in the registry key (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon):

     

    ·         Value AutoLogon needs to be created and set to 1.

     

    ·         Value DefaultPassword needs to be created and set to .

     

    ·         Value AltDefaultPassword needs to be created and set to .

     

    ·         Value DefaultUserName needs to be updated by copying in the user name.

     

    ·         Reboot the computer to log in with the new default user name.

     

    Install the application.

     

    Pass criteria: Application’s primary functionality works successfully for the testing scenario. If supplementary functionality fails gracefully and there is a reasonable workaround to avoid affecting primary functionality, then that is not a fail. To pass testing for full Unicode compliance, the application must function correctly not just fail gracefully.

     

    Client/Server matrix: Based on the functionality and characteristic of the Server app, proper mix of Client /Server test matrix should be prepared.

     

    Generate Unicode characters from multiple language scripts: please use the Tools described in the above section to generate Unicode strings for different language scripts

     

    Test Cases

    This section includes the following test cases:

     

    For Unicode Compliance Applications

     

    TC1.5.1 Support successful installation on any language of OS under any system locale and user locale

    TC1.5.2 Perform all primary functionality on dynamically configured Multi-lingual environment

    TC1.5.3 Support Users belonging to localized security group, with User name composed of Unicode characters from multiple language scripts

    TC1.5.4 Support File I/O to Folders names composed of Unicode characters from multiple language scripts

    TC1.5.5 Support printer names/paths that are composed of Unicode characters from multiple language scripts

    TC1.5.6 Support Network shares, URI/URLs that are composed of Unicode characters from multiple language scripts

     

    For non-Unicode Compliance Applications (suppose the application is to be certified for language X that it specs to support)

     

    TC1.5.7 Install and perform primary functionality successfully on language X localized OS under matched system locale and user locale with a user name composed of Unicode characters from language X script

    TC1.5.8 Support Users belonging to localized security group, with User name composed of Unicode characters from language X script

    TC1.5.9 Support File I/O to Folder names composed of Unicode characters from language X script

    TC1.5.10 Support printer names/path that composed of Unicode characters from language X script

    TC1.5.11 Support Network shares, URI/URLs that composed of Unicode characters language X script

    Tools 

    Snapshot Tool is a Microsoft tool to create snapshots of the File system and registry.By comparing two snapshots, users can find changes that have occurred to the system during the time between the snapshots. This tool is currently under development and will be available soon.  

    Application Compatibility Toolkit 5.0. The Application Compatibility Toolkit (ACT) enables software developers, independent software vendors (ISVs), and IT professionals who work in a corporate environment to determine, before rolling out within the organization, whether their applications are compatible with a new version of the Microsoft® Windows® operating system. ACT also enables such individuals to determine how an update to the new version will impact their applications. For Protected Mode Internet Explorer testing, we utilize a tool called Internet Explorer Compatibility Test Tool which logs security issues that an application should fix prior to being Certified for Logo. The tool is included as part of ACT 5.0. http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/default.mspx 

     AppVerifier. Is a Microsoft tool that is a runtime verification tool for unmanaged code that assists in finding subtle programming errors that can be difficult to identify with normal application testing. The setting of AppVerifier checks requires administrative privileges.  

    DTM. Driver Test Manager (DTM) is a collection of software components that provide a harness to run tests on your driver for the Windows Logo Program.To qualify for the Windows Logo Program, products must pass testing with DTM:     For a device logo, the device must pass tests that verify the reliability and performance of the device.     For a driver quality signature, the driver must meet all the criteria and design requirements defined by Microsoft for drivers that run on Windows.     For a system logo, all devices and drivers in the system must have their respective device logos or driver quality signatures, and the system must pass an additional series of tests.http://www.microsoft.com/whdc/DevTools/WDK/DTM.mspx 

    HATT. High Availability Test Tool. A tool to test high availability solutions in the form of clustering, network load balancing, or other resource recovery techniques. This tool introduces scripted fail conditions for computers and processes so that applications running on Windows can be evaluated for how well they deliver resources under stress. You can download the HATT from this site: http://go.microsoft.com/fwlink/?LinkId=20390. 

    HCT. Hardware Compatibility Test kit. Produced by WHQL (Windows Hardware Quality Labs) the HCT includes documentation and tests that hardware manufacturers can use to design and test products for compatibility and interoperability with Windows operating systems. HCT has been superceeded by DTM, which can be downloaded from:http://www.microsoft.com/whdc/DevTools/WDK/DTM.mspx 

    TaskKill.exe. A system tool to terminate an application or process without allowing graceful shutdown.

    Orca. Is part of the Windows Server 2003 R2 Platform SDK and is a database table editor for creating and editing Windows Installer packages and merge modules. Orca requires administrative privileges to run. 

    RegDump. Is a command line tool that is useful in dumping the contents of registry to a file which can used for analyzing the values/data, taking snapshots of the contents (which can be diffed using regdiff.exe) and monitor (to check for corruption). This tool in conjunction with regdiff can be used by developers/testers to make sure that their component is not changing registry in any undesirable way. This tool will be supplied by Microsoft as part of the Vista Logo test tools.http://download.microsoft.com/download/d/2/5/d2522ce4-a441-459d-8302-be8f3321823c/LogoToolsv1.0.msi 

    RegDiff. Is a command line tool that generates the log of differences found in each file. It compares differences section wise as generated by RegDump tool. This tool will be supplied by Microsoft as part of the Vista Logo test tools. http://download.microsoft.com/download/d/2/5/d2522ce4-a441-459d-8302-be8f3321823c/LogoToolsv1.0.msi 

    Resource Hacker 3.4. Is a freeware tool that can be used to explore resources used for any application executable. This tool can be downloaded from http://www.download.com/3000-2352-10178588.htm or another safe download site.  

    Restart Manager Tool. Is a command tool that is used to inject a shutdown message to the application or service through the RMShutdown API. This tool will be supplied by Microsoft as part of the Vista Logo test tools. 

    SignTool. Is part of the Windows Server 2003 R2 Platform SDK and is a command-line tool that digitally signs files, verifies signatures in files, or time stamps files. 

    ThreadHijacker. Is a command line tool that injects crashes into another process by: pausing a thread, injecting binary data into that process' address space, setting the thread's instruction pointer to that binary data, and resuming the thread.

    分享到:

    历史上的今天: