The Technical Committee has developed the following tools and test cases to help ISVs test their applications on Microsoft Windows.
Client Simulator
Developed by The Technical Committee (The TC), the Client Simulator is an application designed to emulate the suggested behavior of a browser, media or mail client on Windows Vista operating systems, when registering and handling its defaults. A description of correct client behavior can be found in the MSDN library at Guidelines for Managing Default Applications in Windows Vista and on MSDN at TC ISV Tests for Middleware Windows Vista Readiness.
The primary end user of the Simulator is the Independent Software Vendor (ISV) developer. For such a developer, the Simulator offers concrete guidance on creating, revising or publishing a browser, mail client, or media player application for Windows Vista.
ISV Readiness Tests
The Technical Committee (TC) has created a process for assessing how ready third-party applications are on Windows Vista. This effort has culminated in a precise definition of readiness , and a set of tools for verifying readiness. A Windows Vista-ready application must pass a set of “Basic Readiness” tests. Basic readiness consists of correct registration in and correcting functioning of:
- Set Program Access & Computer Defaults (SPAD)
- Default Programs
- Shortcuts (Start Menu, Desktop, Quick Launch, Notification Area, Folder Task Band)
In addition to this “Basic Readiness”, applications are “Good Citizens” if they pass an additional set of tests. Good Citizenship requires an installation and first run experience that respects user defaults. The test cases in Good Citizenship require a competitor or rival application.
ISV Settings Manager
Developed by The Technical Committee (The TC), the ISV Settings Manager (ISM) is an application designed to assist developers in making correct registry settings for their applications on Windows XP and Windows Vista. It assembles registry keys gleaned from MSDN.
Frequently, third-party applications designed for the Windows platform suffer limited visibility and functional availability. After installing such an application, a user experiences difficulty in discovering the application on the main user surfaces – start menu, quick launch, desktop, folder task band and notification area. The user may experience further difficulty in making that application the default for functions like Auto Play, File Associations and Open With. As a result, other applications that are better designed for the platform enjoy prominent selection even when competing applications exist.
The ISM houses all the registry settings needed for applications to attain equal visibility and manage defaults on Windows XP and Windows Vista operating systems. While this information is scattered throughout MSDN, the ISM centralizes this information so that developers have an easier job discovering and selecting registry settings for their applications.