PROCEDURES

Example 1: A Typical Procedure Section from a program with extensive data.

"We clicked on all of the links on the main screen and navigated through the various parts of each section of the program. On a few machines, we did extensive testing of the Search portion of the dictionary, selecting word after word, doing searches, and printing out the definitions. On the other machines, a brief test was done to check compatibility with different system configurations and video cards."

Example 2: A Procedure Section for a slide-presentation program that uses the PowerPoint Viewer.

"Our testing focused mainly on the installation and functionality of the product on each platform. We completely checked all of the chapters and figures on one system for each of the various platforms. We did a limited test routine on the remaining systems."

Example 3: A Procedure Section for a complex, multi-platform school product.

"Our testing focused mainly on the functionality of the product in the different combinations of installation options and operating systems. We did full and concise tests as follows:

For each platform/operating system, we did at least one full installation and one partial CD-ROM installation. The tests on the Windows side completed normally. However, there were problems on the Macintosh side that forced us to cut short the tests on several platforms. The Mac with System 7.6 ran so slowly as to be almost unusable, so the test was terminated after an hour or so. The two iMacs used have System 8.6, and we found it very hard to run the program for any length of time on these without crashing, so these tests were cut short. The Mac product ran well only on the G4 with System 9 and the G3 with System 8.5."

There is extensive detail about the problems with the Macs in the "Operational Problems in Macintosh Only" section.

Finally, many errors were noted about cut-off text that were omitted from this report, since you said that you already knew about them, and that a general fix had been applied."