This document was born out of requests from ISV customers the Windows Readiness lab team has worked with for the past several years. When working with ISVs we frequently get the question “What should we test to be sure we’re compatible?” A good approach would be to perform use case testing against your application. However, there are target areas where we see a large number of applications fail. This document hopes to capture most of the problem areas. We leverage concepts and tests from the Windows logo programs starting with Windows Vista. The logo program has evolved over time and Windows 7 logo has changed in size and has moved to an automated way of testing. You can leverage the automated tools to do some of the core scenarios outlined in this document.
In each test, we try to give recommendations on how to find as many issues with your application as possible. By nature, Windows is a very open and versatile platform. There is no standard set of requirements or tests that all applications have to abide by. For example, we recommend that you test your application as a standard user. If your application is an administrative tool, testing as a standard user is likely not a valid test scenario.
Finally, we make assumptions on how your application should behave based on general best practices. There may be a design reason that restricts you from implementing a best practice. Some best practice may not apply to your application. The goal of the document is to outline an overall set of tests for a “well behaved” Windows application.
|