Adaptable Process Model Checklists: Testing GUIs
	IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.
	Testing GUIs Modern software applications often have sophisticated user interfaces. Because the number of lines of code (or reusable components) required for GUI implementation can often exceed the number of lines of code for other elements of the software, thorough testing of the user interface is essential. . For this checklist, the more questions that elicit a negative response, the higher the risk that the GUI will not adequately meet the needs of the end-user. For windows: Will the window open properly based on related typed or menu-based commands? Can the window be resized, moved, scrolled? Is all data content contained within the window properly addressable with a mouse, function keys, directional arrows, and keyboard? Does the window properly regenerate went it is overwritten and then recalled? Are all functions that relate to the window available when needed? Are all functions that related to the window operational? Are all relevant pull-down menus, tool bars, scroll bars, dialog boxes and buttons, icons, and other controls available and properly displayed for the window? When multiple windows are displayed, is the name of the window properly represented? Is the active window properly highlighted? If multitasking is used, are all windows updated at appropriate times? Do multiple or incorrect mouse picks within the window cause unexpected side effects? Are audio and/or color prompts within the window or as a consequence of window operations presented according to specification? Does the window properly close? For pull down menus and mouse operations: Is the appropriate menu bar displayed in the appropriate context? Does the application menu bar display system related features (e.g., a clock display)? Do pull-down operations work properly? Do break-away menus, palettes, and tool bars work properly? Are all menu functions and pull down subfunctions properly listed? Are all menu functions properly addressable by the mouse? Are text typeface, size and format correct? Is it possible to invoke each menu function using its alternative text-based command? Are menu functions highlighted (or grayed-out) based on the context of current operations within a window? Does each menu function perform as advertised? Are the names of menu functions self explanatory? Is help available for each menu item and is it context sensitive? Are mouse operations properly recognized throughout the interactive context? If multiple clicks are required, are they properly recognized in context? If the mouse has multiple buttons, are they properly recognized in context? Do the cursor, processing indicator (e.g., an hour glass or clock), and pointer properly change as different operations are invoked? Data entry: Is alphanumeric data entry properly echoed and input to the system? Do graphical modes of data entry (e.g., a slide bar) work properly? Is invalid data properly recognized? Are data input messages intelligible? Return to Checklist Table of Contents