1 Normal User interface check list

Test Procedures Results

case ID Pass/Fail

1. Go to page function, first, previous, next and last function,

they should be correct
2. Check all the fields labels, Label Names should be aligned to
Init Capital but exclude Preposition (eg. Port of Loading,
Client Request No.)
All the logogram should be consistent.
For example Align labels (Number, No., #) to No. or #
Another example: PO, RFQ
3. Check all the button names, they should be verb and should
be aligned to Init Capital
(eg. Print View, Save As)
4. Check all the tab name, sub tab name, column heading, Web
page titles and Web navigational elements, they should be
aligned to Init Capital but exclude Preposition
5. Command buttons in the group should be right-aligned. The
exception is for dialog boxes, where command buttons should
be centered at the bottom of the dialog
6. Usually when information is positioned vertically, align fields
by their left edges. The special instance is that number should
be right-aligned . Numbers with decimal values should be
aligned at the decimal point.
7. When there is table list, if any command button handles
multiple records, check box should be added before record
and “select all” check box should exist in column header,
otherwise, radio button should be added.
8. The title text for the pop up window should be aligned to Init
Capital but exclude Preposition.
9. Dialog style pop up window should be used in the following
condition: user will complete some tasks in the pop up
window, for example: select a role, input some data…
10. If user only selects data in the pop up window, include OK
and Close button. The buttons should be on the bottom of the
box and in the center

11. If user input data in the pop up windows and the data actually
are saved, include Save and Close button. The buttons
should be on the bottom of the box and in the center

12. For select Date page, there are two buttons: Set Empty and
Close. The buttons should be on the bottom of the box and in
the center
13. If user have to make a choice, include a command button for
each option. Include OK and Cancel buttons only when the
user has the option of continuing or stopping the action.
14. For other pop up windows which user will do more actions in
the windows except input data or only select data, developer
can add other buttons in the window according to the actual
conditions, And developer can arrange the button location
according to the actual conditions.
15. Normal pop up window should be used in the following
condition: user will only view information in the pop up
window,.
16. Use the plural form of a word rather than using "(s)" (or use
both the singular and plural forms).
17.
Use consistent phrasing for similar situations.
18.
When the user requests changes or deletion of the data, offer
the option of maintaining the old value before making the
change. That is, apply the save or cancel selection to the user
19.
In particular part, each item in a list box or combo box should
be in ascending or an appropriate order of the domain.
20.
In our system, we can include both hyperlinks and command
buttons in our interface. As a general rule, use hyperlinks for
navigating to locations and buttons for carrying out actions.
21. For Navigation bar, system should first display module name,
and then sub module name, and then display the selected
application name or object name for user to return to last
location easily. If sub tab exist in an object , System shall
show current object name and current sub-tab in the
navigation bar, both of which are not hyperlink
No close button will be used to close the current page and
return to the last page. Usually we use symbol “>” to connect
each item in navigation bar.
22.
In a system, the button label should be consistent and
informative. For example, in all editable pages, we use button
save. For all actions to create a new object, we use New
button. For all actions to add an existed object to another
object, we use Add button. In all search criteria page, we use
two buttons: Search and Clear.
23. System should list object name under navigation bar if user
select an object. If no object is selected, for example, begin a
new action, we should define an appropriate page title text-
schedule creation (for example) and locate it at the place of
the object name.
24. Check the spelling of all the words; check the expression of
the entire sentences.
They should be correct
25. Check all the object contents or document contents, all the
fields defined in fields definition documents should appear in
related section, the name should be consistent with the
requirement
26. Check the book title capitalization (first letter of each word) for
the following conditions:
1) Column headings
2) Command button labels
3) Tab names and sub tab name
4) Title bar text
5) Web page titles and Web navigational elements
6) Text box labels (exclude preposition)
7) Check box labels (exclude preposition)
8) Option (radio) button labels (exclude preposition)
27. Check the sentence-style capitalization for the following
conditions :
1) Alternate text (alt text) used to describe images on
Web pages
2) File names
3) Group box labels
4) List box entries
5) Messages
6) Status bar text

28. Check the date field format. The date format should be mm-
dd-yyyy. There are 4 decimal digits for Price($), 2 decimal
digits for Rate(%).

29. Provide visual feedback when the user selects an item to

enable the user to distinguish it from items that are not
selected.

30. All fields that can popup window should have a button (e.g.
View by, completed date should display date calendar
control). Click … button to pop up another window.

31. Check the labels’ names, Display the long names for labels if
space allowed. E.g. use “Minimum Quantity” instead of “Min
Qty”. The longest size of the dropdown list’s value should be
displayed.
32. Almost all the kind of UIs have been defined in the UI
standard, refer to the related kind of UI to check the
consistency(style, color, font, expression method…)

33. Numeric fields in listing should be right justified.