Mobile Client UI Test analysis

With many sites in the client's layout, whether it is the portal, community, shopping sites, such as mobile phone client as a direction of development, mobile phone client only in a small screen, for the mobile phone client UI test with a different way of testing the site. The UI test has its own specifications and requirements from the start interface of the client to the running process until exiting.

Mobile Client testers work in the product process:

Common test points for mobile client UI testing:
1. At various resolutions, the display is normal. The market is the mainstream of Symbian V3 system mobile phones, 240*320, 320*240. The WM system is mainly 240*320 and 320*480. The Android system is mainly 320*480,iphone system for 320*480. In which systems the products are run before the design is determined. Tests will test the effects on different models for different screens on the UI.

2. Front color and background colors with a reasonable coordination, contrast should not be too large, preferably less dark, such as: red, green, etc., commonly used color to consider the use of mobile phone system interface tones. For the UI in the design of color, the test 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 errors, here the error is refers to the picture color and mobile phone system collocation, whether with the idea of visual design source.

3. Buttons that are not related to the operation in progress should be added to the mask (shown in gray in Windows Mobile), perhaps to the interface of the WM system, to different systems, and to the UI test, and how to do the UI test for the mobile interface is more important when it comes to satisfying the phone's characteristics.

4. The control's focus is clearly different from the border of the non-focus state. For the focus on the control, the borders under different colors are strictly required. That is, when checked 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 very easy to lose patience, a short hint is to let users continue to stop on the current page, while friendly UI hints are also important.

6. For illegal input or operation should be sufficient hint, hint, warning or error description should be clear, clear, appropriate pop-up warning screen, but the impact can not be too strong.

7. The accuracy of the text description: A. Whether the text description is consistent with the corresponding function; Typos。

8. Consistent unification of text terms: the options for the parent window are consistent with the child window headings.

9. Product Help documentation: A. Consistent with product features and screenshots, when repackaging the new system, timely update product help group documents; B. document format; c. Technical support should be provided in the help, and it is easy to find new ways of help once the user is difficult to resolve.

10. Product copyright and trademark logo and text statement (generally in the launch interface or software PRODUCT "about" option), involving the company's image and brand, must standardize standardization.

11. To provide users with a custom interface style, the user chooses the color and font. Meet different user habits while satisfying users for some color deviations (such as weakness users).

Test process:
1. Understand the business and UI specifications for the entire product based on the UI specification documentation provided and PRD.
2. Develop and provide a demo that has been designed.
3. If it is a single demo and does not involve business processes, skip to 5th or skip to 4th.
4. Test with the business process in PRD and the UI specification, and submit the found bug, followed by 7th.
5. Test the submitted demo page with a UI specification document and submit a bug.
6. The subsequent demo pages are integrated to test according to PRD's business and submit bugs.
7. Trace the bug back to the test.

The client is assembled from a variety of mobile controls, and excellent UI design also captures the UI optimization of the control to achieve product optimization. For some mobile phone interface commonly used controls, in the normal state, select the status of a variety of conditions, such as the common effects show:

Source: http://www.537520.com/?p=452