Common test points for mobile client UI testing

1. The display is normal at various resolutions. On the market is the mainstream Symbian V3 system mobile phone for 240*320, 320*240. The WM system is mainly 240*320 and 320*480. The Android system is mainly for the 320*480,iphone system for 320*480. What systems are running on some screens before the product determines the design. The test will test the effect on different models of the UI under different screens.
2. The foreground and background color with reasonable coordination, the contrast should not be too big, preferably less dark, such as: Red, Big green, etc., commonly used color to consider the use of mobile phone system interface tones. For the UI in the design of the use of color, testing can put forward a lot of valuable advice, only the picture running in the mobile phone system can better distinguish the UI design of the picture will produce error, here the error is whether the color of the picture with the mobile phone system, whether with the idea of visual design has a source.
3. Buttons unrelated to the ongoing operation should be added to the mask (shown in gray for Windows Mobile), perhaps to the interface of the WM system, to different systems, to the UI test, and, in the case of phone features, how it is more important to test the UI of a mobile interface.
4. There is a noticeable difference between the focus of the control and the bounding rectangle of the non-focus state. For the focus on the control, the borders under different colors have strict requirements. That is, when selected and unchecked, the UI is different for the control, which is more demanding for UI testing.
5. Long operation (download, upload, update, login, etc.), to have a clear dynamic indicator logo or text (for example: Loading ... , etc.), indicating that the operation is in progress. Mobile phone access speed without a PC fast, for mobile phone small screen is easy to lose patience, a short hint is to let users continue to stop on the current page, while the friendly UI prompts also appear to be very important.
6. For illegal input or operation should have enough hints, hints, warnings or error description should be clear, clear, appropriate out of the warning screen, but the impact can not be too strong.
7. Accuracy of text description: A. The text description is consistent with the corresponding function; b. Typos.
8. Uniform unification of text terms: the option of the parent window is consistent with the child window title.
9. Product Help documentation: A. Consistent with product features and support, when repackaging new systems, update the product group documentation; B. document format; c. Help should provide technical support, once the user is difficult to solve can easily find new ways to help.
10. Product copyright and trademark logo and text declaration (generally in the start-up interface or software products "about" option); involving the company's image and brand, must standardize standardization.
11. To provide users with a custom interface style, by the user to choose their own color and font. Satisfy different user habits while satisfying the user for some color deviations (such as blindness users).

Common test points for mobile client UI testing