Guide

        Guide for Testing Program Beta Versions

                               19 October 1998
                     Copyright (C) 1998 Rimrock Software
                             All rights reserved

The purpose of this document is to present you (as a Beta tester) with
general guidelines for testing the Beta version of a Windows program. It is
meant to provide guidelines for a variety of different styles of programs.
Please ignore the sections that don't apply to the program you are currently
testing.

This document is divided into several sections. Each section concentrates on
a different portion of the program - not a physical portion, but a category
of interface or operation.

It might be useful to make a printed copy of this document, so you can refer
to it as you are evaluating the program.

Top

        Section          Category
        =======          ====================================================
           1             Installation and Uninstall
           2             General Program Considerations
           3             Program Functionality
           4             Dialogs
           5             Child Windows
           6             Standard Buttons
           7             Edit Fields
           8             Toolbars
           9             Pull Downs and List Boxes
          10            Text Areas
          11            Data Grids
          12            Menus
          13            Checkboxes and Radio Buttons
          14            General Labeling
          15            Notebooks and Tabs
          16            Tip of the Day Dialog


Section 1. Installation and Uninstall
=====================================

This section provides ideas about the kinds of things to look for during the
installation and uninstall processes.

A. Does the installation process completely describe what is being installed
   and where it is being installed?

B. Does the installation process overwrite newer files with older versions of
   the files?

C. Does the installation process allow you to make backups of files that it
   replaces with newer versions?

D. Does the license agreement screen of the installation process have a "No,
   I don't Agree" button?

E. Does the installation process force you to install the software on a
   particular disk drive or directory?

F. Does the uninstall process completely uninstall all files that it has
   created? This would not include data created by the program during its
   use.

G. Does the uninstall process optionally allow you to not uninstall shared
   files such as DLLs?

Go to Top of the page

Section 2. General Program Considerations
=========================================

This section provides ideas about items to look for, concerning the general
program look and feel.

A. Is the main program window laid out in such a manner as to present the
   work in a logical and easy to understand manner (work flow)?

B. Do all viewable sections of the program fit in a minimum Windows
   configuration (640 X 480)?

C. Unless the program is specifically concerned with high resolution, high
   color graphics, does the program support the minimum Windows color
   configuration of 16 colors?

D. Can the main program window be resized to aid in user work, if necessary?

E. Are visual cues, such as buttons with images on them, easy to understand?

F. Are the visual cues backed up by textual cues, such as floating hints or a
   help/status line?

G. Is all text in all windows and dialogs correctly spelled?

Go to Top of the page

Section 3. Program Functionality
================================

This section provides things to look for concerning the functionality of the
program, i.e., what the program does and how it does it.

A. Does the program completely perform its intended function?

B. Does the program perform its primary function in a timely manner?

C. Is anything that is vital to the intended functionality of the program
   missing from the program?

D. Does the program provide adequate help facilities? (NOTE: help files may
   not be available during the Beta test period)

E. Does the program provide an adequate method for you to contact Rimrock
   Software to report bugs and suggestions?

F. Does the program provide an adequate method for you to reach the Rimrock
   Software Web site?

G. Does the program provide an adequate method or methods for you to order
   the program? (NOTE: Registered users who are testing the program will not
   see the order form)

H. Does the program provide an adequate method for you to register the
   program and enable full functionality? (NOTE: Registered users who are
   testing the program will not see the registration dialog)

I. When you enter the registration ID, are all program functions enabled?
   (NOTE: Registered users who are testing the program will already see full
   functionality)

J. Can all program functions be accessed using the keyboard instead of a
   mouse?

K. Is there anything you think should be included as part of the program's
   normal functionality?

L. Is there anything you think should be added to the program as a "nice to
   have" function?

Go to Top of the page

Section 4. Dialogs
==================

Dialogs are small windows that ask questions or provide information. They are
usually activated from push buttons or menu item selections. This section
provides ideas about what to test in the layout and operation of dialog boxes.

A. Is the dialog color and general layout consistent with other dialogs in
   the program?

B. Is the dialog window a fixed size? Exceptions to this would be dialogs
   that provide some type of function where the resizing of the dialog would
   make the task easier.

C. Does the dialog have a caption?

D. Is the dialog caption easy to understand?

E. Is the dialog caption consistent with the item used to activate the
   dialog?

F. When the dialog is displayed, does the main program window become disabled?

G. Is the dialog border consistent with borders in other dialogs in the
   program?

H. Is the dialog's keyboard tab order consistent with other dialogs in the
   program?

I. Are each of the dialog's hot keys unique?

J. Can the dialog be closed (canceled) with the Escape key?

K. Can the dialog be closed (canceled) with system Cancel (X) button?

L. Is the dialog window the same background color as the other dialogs in
   the program?

M. Can dialog controls be accessed by keyboard?

N. Does dialog tab order follow left to right, top to bottom convention?

Go to Top of the page

Section 5. Child Windows
========================

Child windows are part of a Windows programming convention called Multiple
Document Interface (MDI). Programs such as Microsoft Word and Excel use this
convention, which allows the user to display and work on many things simul-
taneously. This section provides ideas about what to test in the operation
of child windows.

A. Are MDI child windows lacking Ok, Cancel and Close buttons?

B. Can MDI child windows be tiled?

C. Can MDI child windows be maximized?

D. Can MDI child windows be minimized?

E. Is the current MDI child closed when the main menu Close item is selected?

F. Is the current MDI child completed/closed when the main menu Save item is
   selected?

G. Are MDI child menu items merged into the main menu when the window is
   opened?

H. Are MDI child menu items removed from the main menu when the window is
   closed?

I. Are the MDI child menu items positioned properly in the main menu?

J. Are MDI child controls hints displayed in the parent status bar?

K. Can all form controls be accessed by keyboard?

L. Does the form tab order follow left to right, top to bottom convention?

Go to Top of the page

Section 6. Standard Buttons
===========================

Standard buttons are the normal push buttons in Windows. This section provides
ideas about what to test in the operation standard buttons.

A. Are the buttons the same color in all windows or dialogs of the program?

B. Are the buttons located in the same relative area in each window and
   dialog of the program?

C. Are the buttons labeled in the same order in each window and dialog of the
   program?

D. Are disabled buttons grayed out?

E. Are disabled buttons missing from the keyboard tab sequence?

F. Is there a hot key for every button that requires one? Omit OK, Close and
   Cancel.

G. Is each button hot key unique?

H. Do the buttons lack hints? They should not have any.

I. If a button activates a pull down menu, does the menu appear directly below
   the button?

J. Are the buttons all the same size in all windows and dialogs of the
   program?

K. Are the buttons aligned with one another?

L. Are the buttons spaced the same in all windows and dialogs of the program?

M. Does each dialog have a default button (if appropriate)? A default button
   is one that executes if the Enter key is pressed.

N. Is each button in the program clearly labeled as to purpose?

O. Are the button labels consistent with the rest of the buttons in the
   program?

P. Is there a button which allows the user to leave the dialog without having
   to perform the dialog's function?

Go to Top of the page

Section 7. Edit Fields
======================

Edit fields are small areas the allow you to enter a single line of text.
This section provides ideas about what to test in using edit fields.

A. Do all edit fields in the program have the same background color?

B. Do all non-editable fields in the program have the same background color?

C. Are non-editable fields absent from the keyboard tab order?

D. Do numeric fields only allow numbers?

E. Are numeric fields right justified?

F. Do all alpha fields in the program allow only alphabetic characters?

G. Do all upper case fields in the program allow only upper case?

H. Are all alpha fields in the program left justified?

I. Are the edit fields in a window or dialog aligned with one another to
   present a pleasing and easy to follow appearance?

J. Is each edit field in the program the same relative size as the data to
   be entered into it?

K. Is each edit field in the program labeled as to purpose?

L. Are the edit field labels consistent throughout the program?

M. Do all edit fields lack hints? They should have prompts instead of hints.

N. Does each edit field have a limit as to the number of characters that may
   be entered into it?

Go to Top of the page

Section 8. Toolbars
===================

Toolbars put often used functions into an area where it is easy for the user
to access those functions. The functions are usually presented in the form of
buttons, but may also consist of edit fields, checkboxes, radio boxes or
pull-downs. This section provides ideas about what to test in using toolbars.

A. Are the toolbar functions arranged in some sort of logical order?

B. Are the toolbar functions separated into logical groupings?

C. Are any of the toolbar items in the keyboard tab order? They should not be.

D. If the toolbar is user-modifiable, is this function accomplished in an
   easily-understood manner?

E. If the toolbar functions have only visual cues (such as a push button with
   a bitmap on it), do they also have text cues, such as a floating hint or a
   hint on a status/hint bar?

Go to Top of the page

Section 9. Pull Downs and List Boxes
====================================

Pull downs are edit fields that have a pull down list attached to them. List
boxes look like edit areas, but cannot be edited and contain a single element
on each line of the box. This section provides ideas about what to test in
using pulldowns and list boxes.

A. Do all the pull-downs in the program have the same background color?

B. Can you pull the list down with Alt-down arrow key?

C. Can you pop the list up with Alt-up arrow key?

D. Is the highlighted item selected when the Alt-up arrow key is pressed?

E. Can you pop the list up with the Escape key?

F. Is the highlighted item selected when the Enter key is pressed?

G. Are disabled pull-downs absent from the tab order?

H. Is the pull-down labeled as to purpose?

I. Are the pull-down labels consistent with the pull down labels in the rest
   of the program?

J. Do all pull-downs lack hints? They should have prompts instead of hints.

K. Do all the list boxes in the program have the same background color?

L. Are the list boxes in the keyboard tab order?

M. Do the list boxes all have a vertical scrollbar?

N. If the information presented in the list box is longer than the list box
   is wide, is there a way to see all the information (horizontal scroll bar,
   hint, another window, etc)?

Go to Top of the page

Section 10. Text Areas
=====================

Text areas are places where the user can enter or view multiple lines of
text. This section provides ideas about what to test in using text areas.

A. Do all editable text areas in the program have the same background color?

B. Do all non-editable text areas in the program have the same background
   color?

C. When necessary, are scroll bars present in the text area?

D. Do all text areas lack hints?

E. Are editable text areas in the keyboard tab order?

F. Are non-editable text areas missing from the keyboard tab order?

G. Have Windows clipboard cut, copy and paste functionality been provided for
   editable text areas?

Go to Top of the page


Section 11. Data Grids
======================

Data grids are areas that contain rows and columns of text or graphical
information. These areas are often visual representations of database
information. This section provides ideas about what to test in using data
grids.

A. Do all data grids in the program have the same background color?

B. If the data grid is non-editable, when tabbing into the grid, is the focus
   by row (instead of by data cell)?

C. If the data grid is editable, when tabbing into the grid, is the focus
   by data cell (instead of by row)?

D. Can you tab out of the grid?

E. Does each data grid in the program have a grid header?

F. Is the grid header font the same as the data font? (It can be bolded,
   though)

G. When necessary, are the scroll bars present?

H. Do the data grids lack hints? They should have prompts instead of hints.

Go to Top of the page


Section 12. Menus
=================

Menus are lists of functions to perform in the program. There can be a menu
at the top of the main program window. Some programs also have popup menus
that are activated with a right mouse click. This section provides ideas
about how to test menus.

A. Does the application contain only one main menu?

B. Does each main menu item category have a first letter hot key (underlined
   letter)?

C. Does each main menu item have a hot key?

D. Are subsections of a main menu category delimited by a line?

E. If a main menu category is very long, has it been broken up into submenus?

F. If a main menu item has a shortcut key, is the shortcut displayed with the
   menu item?

G. Does each main menu item have a hot key?

H. Is each main menu hot key unique within its particular menu?

I. Are non-selectable main menu items grayed out?

J. Are all selectable main menu items not grayed out?

K. If present are popup menus activated with a right-mouse click?

L. Does the popup menu appear close to the mouse cursor?

M. Are non-selectable popup menu items grayed out or missing?

N. Are all selectable popup menu items not grayed out or present?

O. Is each popup menu item clearly labeled as to function?

P. Does each popup menu item have a hot key?

Q. Is each popup menu hot key unique within its own menu?

Go to Top of the page


Section 13. Checkboxes and Radio Buttons
========================================

Checkboxes allow singular items to be selected or unselected by checking or
unchecking the box. Radio buttons group items together and allow only one
single item out of the group to be selected. This section provides ideas
about how to test checkboxes and radio buttons.

A. If there are a group of checkboxes, are they aligned with one another?

B. Are non-checkable checkboxes grayed out?

C. Are checkable checkboxes not grayed out?

D. Do all the checkboxes lack hints? They should each be clearly labeled as
   to function, instead.

E. Is each checkbox in the keyboard tab sequence?

F. Can select or unselect a checkbox with the keyboard space bar?

G. Are radio buttons grouped appropriately?

H. Can only one radio button of a group be selected at a time?

I. Are the radio buttons in a group aligned?

J. Are non-selectable radio buttons grayed out?

K. Are selectable radio buttons not grayed out?

L. Do all the radio buttons lack hints? They should each be clearly labeled
   as to function, instead.

M. Is the group of radio buttons in the keyboard tab sequence? A single tab
   should get you into the radio group, and a single tab should get you out.
   Navigation inside the radio button group should be done with the keyboard
   arrow keys.

Go to Top of the page


Section 14. General Labeling
============================

This section provides ideas about how to test the program's labels.

A. Are the labels in a window or dialog all the same font?

B. Is the label font of a window or dialog consistent with the label font of
   other windows or dialogs?

C. Are labels of a window or dialog the same color as labels in other windows
   or dialogs?

D. If a label indicates a hot key, is the label connected to the proper
   control?

E. Is the spelling correct for all labels?

Go to Top of the page


Section 15. Notebooks and Tabs
==============================

Notebooks are used to display multiple pages of information in the same
physical area. Notebook tabs are used to access the various pages of a note-
book.  This section provides ideas about how to test notebooks and tabs.

A. Are the notebook tabs displayed consistently with tabs in other windows or
   dialogs (top or bottom)?

B. Are the notebook tabs labeled clearly and consistently with the rest of
   the program?

C. Does each notebook tab have a hot key?

D. Is each notebook tab hot key unique?

E. Are the general controls for the dialog displayed outside of the notebook
   page?

F. Do the notebook tabs lack hints?


Section 16. Tip of the Day Dialog
==================================

A. Can the Tip of the Day dialog be disabled?

B. Can the Tip of the Day dialog be re-enabled after it is disabled?

C. Are the tips short, to the point, and useful?

D. Does the Tip of the Day dialog have a "Next Tip" and a "Close" button?

Go to Top of the page