V1.0
08/26/99 3:53 PM
Designed by James Bach, Testing Consultant
james@satisfice.com
Satisfice, Inc.
http://www.satisfice.com
Page 1 of 22
General Functionality and Stability
Test Procedure
for Certified for Microsoft Windows Logo
Desktop Applications Edition
This document describes the procedure for testing the functionality and stability of a software
application (hereafter referred to as “the product”) for the purpose of certifying it for Windows 2000.
This procedure is one part of the Windows 2000 compatibility certification process described in
Certified for Microsoft Windows Test Plan.
This procedure employs an exploratory approach to testing, which means that the test cases are not
defined in advance, but rather are defined and executed on the fly, while you learn about the product. We
chose the exploratory approach because it is the best way to test a product quickly when starting from
scratch.
This document consists of five sections:
§ Introduction to Exploratory Testing
§ Working with Functions
§ Testing Functionality and Stability
§ Reading and Using this Procedure
§ Test Procedure
The first three parts explain the background and concepts involved in the test procedure. The fourth
section gives advice about getting up to speed with the procedure. The fifth section contains the
procedure itself.
This document is designed to be duplex printed (two sides on each page). For
that reason, pages 2, 10, and 12 are intentionally blank.
Page 2 of 22
Page 3 of 22
Introduction to Exploratory Testing
With this procedure you will walk through the product, find out what it is, and test it. This approach to
testing is called exploratory because you test while you explore. Exploratory testing is an interactive
test process. It is a free-form process in some ways, and has much in common with informal approaches
to testing that go by names like ad hoc testing, guerrilla testing, or intuitive testing. However, unlike
traditional informal testing, this procedure consists of specific tasks, objectives, and deliverables