Mobile WEB interface and usability testing method

Interface and usability testing

1. Whether the style, style, and color are coordinated
2. Whether the interface layout is neat and coordinated
3. Whether the interface operation and title description are appropriate
4. Whether the operation conforms to people's normal habits
5. Whether the prompt interface conforms to the specification 6. Whether the controls in the interface are aligned
7. Whether the date control can be edited
8. Whether the length of the date control is reasonable, and all the time can be displayed when it has been modified.
9. Whether the column width of the query result list is reasonable and whether the label description is reasonable
10. Query The result list is too wide and there is no horizontal scrolling prompt
. 11. For the text with long information, the text box does not have the function of automatic vertical scroll bar.
12. Is the data entry control convenient
? 13. Does it support the Tab key? 14. Are
there any related hotkeys provided?
15. Whether the prompt description of the control is correct
16. Whether the module calls are unified, and whether the same module calls the same interface
17. When the page is moved with the scroll bar, whether the page controls are displayed normally
18. The correct format of the date should be XXXX-XX-XX or XXXX-XX-XX XX:XX:XX
19. Whether the page has extra buttons or labels
20. Whether the window title or icon is unified with the menu bar
21. The window is maximized 22.
For normal functions, users can use it without reading the user manual.
23. When performing risky operations, there are prompts for confirmation, deletion, etc.
24. Is the operation sequence reasonable ?
25. Correctness check: Check whether the form, button, table, header, footer, prompt information, and other text spelling, sentence grammar, etc. on the page are correct.
26. The system should warn the user and prompt information before the user performs the wrong operation.
27. Check the page resolution, check the system interface friendliness in various resolution browsing systems.
28. Reasonableness check: After doing delete, update, add, cancel, back and other operations, check whether the information returned to the page is reasonable.
29. Check whether the localization is passed: the English version should not have Chinese information, and the English translation is accurate and professional.

Compatibility testing

Compatibility testing not only refers to the compatibility of the interface between different operating systems or browsers, but also takes into account the compatibility of some functional tests, including operating system compatibility and application software compatibility, and may also include hardware compatibility. When it comes to technologies such as ajax, jQuery, and JavaScript, compatibility issues under different browsers must be considered.

Link testing

is mainly to ensure the availability and correctness of links, which is an important aspect of website testing.
Link testing can be performed using specific tools such as XMENU.

Navigation Testing
Navigation describes how the user navigates within a page, between different user interface controls such as buttons, dialogs, lists, and windows; or between different connected pages. Whether a web application is easy to navigate can be determined by considering the following questions: Is the navigation intuitive? Is the main part of the web system accessible through the home page? Does the web system need sitemaps, search engines, or other navigational aids?

Putting too much information on one page can often have the opposite effect of what is intended. Users of Web application systems tend to be purpose-driven, scan a Web application system quickly to see if there is information that meets their needs, and if not, they will quickly leave. Few users are willing to take the time to become familiar with the structure of a web application, so web application navigation aids should be as accurate as possible.

Another important aspect of navigation is whether the page structure, navigation, menu, and connection styles of the Web application system are consistent. Make sure that users intuitively know if there is still content in the web application system, and where the content is.

Once the level of the Web application system is determined, it is necessary to start to test the user navigation function, and the effect will be more obvious if the end user participates in this test.

TestBird