Number Summary Type Steps Test Category Description Test Case Priority Pre-Conditions Test Suite HFI-Related 1 Tabbing within the open window Usability "*Tab through the whole window +Verify that tabbing moves per Windows standards *. +Verify that no area or button is omitted *. +Verify that the focus does not disappear for any of the tabbings" App window- navigation Tabbing should conform to Windows standards High App Windows Navigation 2 Initial focus within the open window Usability "*Open a currently closed window within the application *From the spec, know which element or field is supposed to have focus +Verify that the spec covers this issue *Look for signs indicating focus (such as dotted lines around the element or field; highlighting of the element, etc.) +Verify presence and placement of by one or more methods (pressing the spacebar, hitting the Return button, etc.)" App window- navigation An initial focus should be present and evident on an active element or field High An open window within the application and fields or elements within the window which are capable of having focus App Windows Navigation 3 Exiting the window Usability "*Try exiting the window using the various conventions +Verify that File--->Exit exits and closes the window *. +Verify that clicking the 'windows X' in the upper right corner exits and closes the window *. +Verify that clicking any 'Exit,' 'Cancel' or 'Close' button exits and closes the window" App window- navigation Methods of exiting the window should be conventional, evident and work High App Windows Navigation 4 Return to a previous window Usability "*Open an app window that allows moving directly to a subsequent window *Perform an action that takes you to another window +Verify that there is a way to move back to the previous window *. +Verify that there are clear indicators of the method to move back *. +Verify that either (1) there is no penalty to the user (such as lost data) by moving back to the previous window or (2) the user is clearly informed of the penalty and given a chance to Cancel or to avoid the penalty by first saving the data" App window- navigation When appropriate, a buyer should be given a way to return to a previous window High A UI in which a user can move from one window to another, with the expectation of being able to move back to the previous one App Windows Navigation 5 Undo an action in the current window Usability "*Identify an action that can be done within the window without closing it [entering data, for example] *Perform the action +Verify that the CTL-Z Windows convention undoes the action *. +Verify that Edit--->Undo undoes the action *Identify any 'Undo' button or icon +Verify that clicking on it undoes the action" App window- navigation When not legitimately prohibited, a user should be able to easily undo an entry or an action High An app window containing a function which should be able to be undone App Windows Navigation 10 Making links and 'action triggers' obvious Usability "*Open the app window *Look for any links within the window +Verify that any links are obvious (underlined, different color, etc.) *Look for any buttons in the window +Verify that buttons are obvious *. +Verify that buttons have appropriate labels *. +Verify that buttons are active when they should be *Look for any link-appearing 'action triggers' +Verify that clicking on them performs the promised function ['Logout' for example]" App window- navigation Links, buttons and other 'action triggers' should be obvious and should perform as expected High App Windows Navigation 6 Entering data by typing into a fixed-length field Usability "*Identify a field in the window that is supposed to receive data *Note the type of data required and/or allowed *Enter some appropriate data +Verify that the appropriate data is accepted *Enter some inappropriate data (such as alpha data in a numeric-data-only field) +Verify that the inappropriate data is NOT accepted *. +Verify that the user is given a clear, helpful message so that he can enter correct data *Attempt to enter data that is longer than the allowed amount +Verify that only the allowed amount of data is accepted " App window- data entry Appropriate data of the allowed length should be accepted into a field High An app window having one or more field for user input. At least one field should accept only alpha or numeric data. App Windows Task Flow 11 Entering data by typing into a scrollable text box Usability "*Enter text into all of the visible area of a scrollable text box *Continue typing +Verify that additional data is accepted *. +Verify that the new data is visible due to the older text scrolling up as additonal text is being added *. +Verify that word-wrap is keeping all text in the confines of the box (not clipping it on the right)" App window- data entry Users should be allowed to enter more data than the visible box shows when it is a scrollable text box High Detailed Design 7 Entering data by using a single-choice drop-down choice field Usability "*Click to drop down the single-choice menu *Hold the CTL key down and click on two or more choices *Release the CTL key +Verify that only one of your choices remains selected" App window- data entry Users should only be allowed to choose one item in a single-choice drop-down choice field High App Windows Detailed Design 8 Entering data by using a multi-choice drop-down choice field Usability "*Click to drop down the multi-choice menu *Hold the CTL key down and click on two or more choices *Release the CTL key +Verify that all of your choices remain selected *Without holding the CTL key down, click on any one choice +Verify that the new choice is the only choice now selected (the other choices de-select)" App window- data entry Users should be provided a method of choosing more than one item in a multi-choice drop-down choice field High App Windows Detailed Design 9 Validating data that is entered Usability "*Enter some disallowed characters into a field (such as *@$%/\!") +Verify that the inappropriate data is not accepted \+Verify that some clear and useful message is given to the user"" App window- data entry Users should be corrected and helped when they enter disallowed characters High A set of one or more disallowed characters are prohibited from being entered into one or more (possibly all) fields in a window. App Windows Task Flow 12 Providing the user with feedback for having entered data Usability "*Enter data into a field *Look for any methods used to provide feedback to the user, such as- +The letters and words show in the field as they are being entered *. +(Optional) Sounds are (or can be) associated with the input (such as typewriter clicks, etc.)" App window- feedback to user Users should receive evidence that data they are inputting has been received by the application High App Windows Task Flow 13 Triggering appropriate error alerts Usability "*Generate a error message by creating an error condition +Verify the message identifies the user action or system condition that occurred *. +Verify it defines the circumstances under which the message appears" App alerts- conditons Error alerts should make users aware of the conditions or actions that triggered the alert High App Windows Task Flow 14 Clearly defining the type of messagee Usability "*Generate a error message by creating an error condition +Verify the message identifies the specific type of alert: Information, Error, Question, Warning, Status" App alerts- message type Message type should be clearly identified and appropriate (within the usage context) High App Windows Task Flow 15 Anticipating the impact of the message on the user Usability "*Generate an alert message +Look for 'alarming' words that far exceed the actual danger, ALL-CAP words with lots of !!! after them, etc." App alerts- tone Message should not be "alarming" in message and style High App Windows Task Flow 16 Having clear and useful alert messages Usability "*Generate an alert +Verify its wording is clear, concise and unambiguous *. +Verify it contains no mysterious code numbers or names *. +Verify it uses appropriate terms *. +Verify it provides clear examples, if needed" App alerts- wording Message should be clear, complete and useful High App Windows Task Flow 17 Having self-contained alert messages Usability "*Generate an alert +Verify it does not refer users to outside Help sources unnecessarily" App alerts- completeness Alert messages should be self-contained whenever possible High App Windows Task Flow 18 Placement of the Sharp logo Usability "*Open each of the app windows that show the Sharp logo +'Verify that the window displays the Sharp logo *. +Verify that the logo is the currently approved one *. +Verify that the logo is placed in one of the approved places in the window" User Interface - High Level The Sharp logo should be used correctly and according to company policy and style guides. High App Windows Branding 19 Spelling and grammar Usability "*Open each of the app windows +Verify that all words are spelled correctly *. +Verify that correct grammar has been used *. Verify the absence of technical jargon, colloquialisms, slang" User Interface - High Level Correct spelling and grammar are musts for all Sharp Uis High App Windows Branding 20 Color scheme Usability "*Open each of the app windows +Verify that the color scheme is consistent with other Sharp products *. +Verify that the color scheme is consistent within the product under test" User Interface - High Level The color scheme should be consistent High App Windows Branding 21 Active and Inactive menu items and buttons Usability "*Open each of the app windows +Verify that buttons and menu items in the active state should be *. +Verify that active buttons and menus appear active *. +Verify that buttons and menu items in the inactive state should be *. +Verify that inactive buttons and menus appear inactive" User Interface - High Level Buttons and menu items should be in an active or inactive state and this state should be obvious to the user High App Windows Navigation 22 Title bars as part of an app window Usability "*Open each of the app windows +Verify that it has a title bar at the top *. +Verify there is a meaningful title in the title bar" User Interface - High Level App windows should have title bars and they should be meaningful High App Windows Structure 23 Application window has System Menu Usability TBD User Interface - High Level Some app windows should have a System menu High App Windows Structure 24 Status bars as part of an app window Usability "*Open an app window +Verify there is a status bar along the bottom of the window *. +Verify status bars appear only along bottom of a window *. +Verify status bars include only non-critical information [see comment] *. +Verify when there is no interesting status to report, status bar panel is blank *. +Verify status bars are not used in dialogs, alerts or other secondary windows" User Interface - High Level For app windows which have status bars, they should be used properly. High App Windows Structure 25 Methods of manipulating a window Usability "*In the upper right corner of each window is an icon for manipulating the window. +Verify the window has a 'Windows X' on the upper right corner of the window for closing it *. +Verify the window has a minimize icon *. +Verify the window has a maximize icon *. +Verify the window has a restore icon *. +Verify the icons are disabled when the window is in that particular state " User Interface - High Level App windows need an accepted way to be opened, closed, minimized, maximized and restored. High App Windows Task Flow 26 Informing the user of processing delays Usability "*Perform tasks whose processing times are lengthy +Verify that If the length of a task can be predicted, ameasured progress bar is used *. +Verify that if the length of task cannot be predicted a, indeterminate progress bar is used" User Interface - High Level Users should be informed of processing delays and, where feasible, be given some indication of how far the process is along (in either relative or absolute terms). High App Windows Task Flow 27 Links, URLs Usability "*Open an app window that contains links or URLs +Verify that links are visible *. +Verify that links indicate their status (never visited, visited) *, Verify that clicking on the link takes the user to the expected location (target)" User Interface - Links Internal and external links should be apparent, show their status and work correctly High App Windows Task Flow 28 Default values for fields Usability User Interface - Data Input User-editable fields should indicate their 'default' value (if any) to the user. High This assumes that one or more user-entered fields has a default value and a clear way to indicate that default value. App Windows Task Flow 29 User adding own choice allowed/ disallowed Usability User Interface - Data Input Users should be informed when adding their own choice is or is not an option when presented with a set of pre-existing choices in the UI. High App Windows Task Flow 30 Accuracy of graphic portrayals Usability User Interface - Graphics Graphic portrayals of expected results should be accurate (for example, N-Up Portrait, N-Up Landscape) High App window to be tested must have some 'expected result' graphics that change based on what selections the user makes. These could include N-Up, margin adjustments, etc. App Windows Task Flow 31 stickiness (retained data) Usability User Interface - Data Input User should be made aware of the effect on his already-input data in various error scenarios High This assumes the user's ability to force a window to close, or to navigate away from a window, after having input data into one or more fields. App Windows Task Flow 32 Informing user of irreversible actions Usability User Interface - Graceful Failure Users should not be able to perform potentially detrimental actions that are irreversible without first being warned High This assumes the user's ability to perform an action that logically and possibly could be to her detriment. Examples could include cancelling an install, deleting data that will not be recoverable, doing an action that cannot be undone programatically. App Windows Task Flow