I. Overview
The user interface refers to the visible appearance of the software and the parts (menus, dialog boxes, windows, and other controls) that interact with the user at the bottom. User interface testing, also known as UI testing, aims to ensure that the user interface will provide users with corresponding access or browsing functions through the functions of the test object.
Second, detailed explanation
The interface is the most direct layer between the software and the user. The quality of the interface determines the user's first impression of the software. And a well-designed interface can guide users to complete the corresponding operations themselves, and play a role as a guide. At the same time, the interface is like a human face, which has the direct advantage of attracting users. A well-designed interface can bring users a sense of ease and joy and a sense of success. On the contrary, due to the failure of the interface design, the user feels frustrated. No matter how useful and powerful functions are, the user's fear and abandonment may be in vain. The current interface design is far from enough to attract the attention of software designers. It was not until the recent rise of web page production that it was favored by experts. And a well-designed interface is rejected due to the need to have a talent for artistic beauty. There are currently three popular interface styles: multi-window, single-window, and resource manager style. Regardless of the style, the following rules should be taken seriously.
| rule |
Overview |
Rules |
| Ease of use |
The button name should be easy to understand, use accurate words, avoid ambiguous words, and be easy to distinguish from other buttons on the same interface. It is best to be able to understand the meaning of the text |
1): Buttons that complete the same or similar functions are framed with Frame, and frequently used buttons must support shortcuts. 2): The elements that complete the same function or task are placed in a centralized location to reduce the distance of the mouse movement. 3): Divide the interface into local blocks according to functions, enclose them in Frames, and have function descriptions or titles. 4): The interface should support the keyboard automatic browsing button function, that is, the automatic switching function of pressing the Tab key and the Enter key. 5): The controls that should be entered first and important information on the interface should be in the front of the tab order, and the position should also be placed in a more eye-catching position on the window. 6): The number of controls on the same interface should not exceed 10. If there are more than 10, you can consider using the paging interface display. 7): The paging interface should support quick switching between pages, commonly used shortcut keys Ctrl+Tab. 8): The default button should support Enter and select operations, that is, the corresponding operation of the default button will be automatically executed after pressing Enter. 9): The writable control item should give an explanation after detecting an illegal input and automatically get the focus. 10): The order of the Tab key must be the same as the order of the controls. At present, the most popular way is from top to bottom, and from left to right between lines. 11): The check box and the option box are arranged in order according to the high and the bottom of the selection probability. 12): The check box and option box should have default options and support Tab selection. 13): When the number of options is the same, use the option box instead of the drop-down list box. 14): Use the drop-down box instead of the option box when the interface space is small. 15): Use the option box when the number of options is small, instead use the drop-down list box. 16): Professional software should use related professional terminology, and the universal interface advocates the use of universal terminology. |
| Normative |
Usually the interface design is designed according to the Windows interface specifications. It can be said that the higher the standardization of the interface, the better the ease of use. |
1): Common menus must have command shortcuts. 2): The menus that complete the same or similar functions are opened in the same position separated by a horizontal line. 3): The icon in front of the menu can intuitively represent the operation to be completed. 4): The menu depth is generally required to be controlled within three levels at most. 5): Toolbar requirements can be customized according to user requirements. 6): Put together toolbars with the same or similar functions. 7): Each button in the toolbar must have prompt information. 8): The longest length of a toolbar cannot exceed the width of the screen. 9): The icons in the toolbar can intuitively represent the operations to be completed. 10): Set the default placement position of the toolbar commonly used by the system. 11): When there are too many toolbars, consider using the toolbox. 12): The tool box should be able to increase or decrease, which can be customized by users according to their needs. 13): The default total width of the tool compartment should not exceed 1/5 of the screen width. 14): The status bar must be able to display the information that the user actually needs. Commonly used ones are: current operation, system status, user location, user information, prompt information, error information, etc. If an operation takes a long time, it should Show progress bar and progress prompt. 15): The length of the scroll bar can be changed in time according to the length or width of the displayed information, so that the user can understand the position and percentage of the displayed information. 16): The height of the status bar is suitable for placing five good characters, and the width of the scroll bar is slightly narrower than that of the status bar. 17): There must be a clear boundary between the menu and the toolbar; the menu is required to be displayed protrudingly, so that there is still a three-dimensional effect when the toolbar is removed. 18): The font size 5 is usually used in the menu and status bar. The toolbar is generally wider than the menu, but don't be too wide, otherwise it looks very uncoordinated. 19): The right-click shortcut menu adopts the same criteria as the menu. |
| Help facility |
The system should provide detailed and reliable help documents, and users can find solutions by themselves when they are confused. |
1): The performance introduction and description in the help file should be consistent with the system performance. 2)：打包新系统时，对作了修改的地方在帮助文档中要做相应的修改。 3)：操作时要提供及时调用系统帮助的功能。常用F1。 4)：在界面上调用帮助时应该能够及时定位到与该操作相对的帮助位置。也就是说帮助要有即时针对性。 5)：最好提供目前流行的联机帮助格式或HTML帮助格式。 6)：用户可以用关键词在帮助索引中搜索所要的帮助，当然也应该提供帮助主题词。 7)：如果没有提供书面的帮助文档的话，最好有打印帮助的功能。 8 )：在帮助中应该提供我们的技术支持方式，一旦用户难以自己解决可以方便的寻求新的帮助方式。 |
| 合理性 |
屏幕对角线相交的位置是用户直视的地方，正上方四分之一处为易吸引用户注意力的位置，在放置窗体时要注意利用这两个位置 |
1)：父窗体或主窗体的中心位置应该在对角线焦点附近。 2)：子窗体位置应该在主窗体的左上角或正中。 3)：多个子窗体弹出时应该依次向右下方偏移，以显示窗体出标题为宜。 |
三、测试点分类
| 录入界面 |
1.1 输入字段要完整，且要与列表字段相符合（参照数据库进行检查） 1.2 必填项一律在后面用*表示（必填项为空在处理之前要有相关的提示信息） 1.3 字段需要做校验，如果校验不对需要在处理之前要有相关的提示信息 （1） 长度校验 （2） 数字、字母、日期等等的校验 （3） 范围的校验 1.4 录入字段的排序按照流程或使用习惯，字段特别多的时候需要进行分组显示 1.5 下拉框不选值的时候应该提供默认值 1.6 相同字段的录入方式应该统一（手动输入 、点选 、下拉选择、参照） 1.7 录入后自动计算的字段要随着别的字段修改更新（如单价变后，金额也变） 1.8 日期参照应该既能输入，又能从文本框选择 |
| 界面格式 |
2.1 字体颜色、大小、对齐方式（根据字段的性质确定）、加粗的一致性 2.2 文本框、按钮、滚动条、列表等控件的大小、对齐、位置的一致性 2.3 所有新增、修改、查看页面加上页面说明（如：XXX新增、XXX编辑、XXX查看等说明字样），（弹出的）界面要有标题，标题与内容要一致 2.4 不同界面显示相同字段的一致性（如列表界面和编辑界面） 2.5 界面按钮显示要求（查询、新增、删除顺序） 2.6 列表的顺序排列应该统一（按照某些特定条件排序） 2.7 下拉框中的排列顺序需要符合使用习惯或者是按照特定的规则排定 2.8 所有弹出窗口居中显示或者最大化显示 2.9 信息列表中如果某个字段显示过长用“…”或者分行显示 2.10 人员、时间的缺省值一般取当前登录人员和时间 2.11 对于带有单位的字段，需要字段的标签后面添加如下内容：“（单位）” |
| 功能问题 |
3.1 按钮功能的实现（如返回按钮能否返回） 3.2 信息保存提交后系统给出“保存/提交成功”提示信息，并自动更新显示 3.3 所有有提交按钮的页面都要有保存按钮（每个界面风格一致） 3.4 凡是点选或者下拉选择的界面，如果一旦选择完了无法回到不选择的情况，需要加上“清除选择”功能按钮 3.5 没有选择记录点击删除/修改按钮要提示“请先选择记录” 3.6 选择记录后点击删除按钮要提示“确实要删除吗？” 3.7 需要考虑删除的关联性，即删除某一个内容需要同时删除其关联的某些内容 3.8 界面只读的时候（查询、统计、导入）等，应该不能编辑 |
| 查询问题 |
4.1 查询条件缺少一些可以查询的字段 4.2 有些查询条件需要支持模糊查询 4.3 需要考虑有些查询条件本身的关联性（即某个查询条件的取值范围是依赖于其它查询条件的取值） 4.4 查询条件名称与信息列表及信息编辑页面相应的字段名称完全统一 4.5 不同模块相同字段的查询方式应该统一（手动输入 、点选 、下拉选择） 4.6 出报表的时候，查询条件需要显示在报表标题的下面，这样看报表的时候知道数据的依据是什么 4.7 对于范围的查询采用全闭的形式（如 [2006-1-1,2006-12-30]） |