Shulou(Shulou.com)06/01 Report--

Where there is software, there will be interface, and there will be interface testing. Interface testing is the most, most tedious and simplest test in software testing. Especially in localization testing (multi-language testing), there are a lot of interface tests.

The user interface test is referred to as the UI test, which tests whether the layout of the functional modules of the user interface is reasonable, whether the overall style is consistent and whether the placement of each control is in line with customer habits, and more importantly, it is convenient to operate, easy to navigate, whether the Chinese characters of the interface are correct, whether the naming is unified, whether the page is beautiful, whether the combination of words and pictures is perfect, and so on.

The purpose of the UI test:

1. Ensure that the user interface provides users with appropriate access or browsing functions by testing the functions of the objects.

2. Ensure that the user interface meets the standards of the company or industry

3. Verify the interaction between users and software through user interface (UI) testing.

4. The goal of UI testing is to ensure that the user interface provides users with appropriate operations to access and browse the functions of the test object.

5. In addition, the UI test also ensures that the objects inside the UI function meet the expected requirements and follow the company or industry standards

In general, we conduct interface testing, directly based on the product prototype diagram and UI cut / effect drawing, to verify whether it is consistent. But if the company does not have a prototype map, how can it be broken without a UI effect? After all, there are too many situations in which we are both miserable people at the end of the world.

Then we can refer to the same type of mature products on the market to do interface comparison, and consider the following aspects:

1. Navigation test

2. Graphic test

3. Content testing

4. Form test

5. Overall interface testing

Then I share the test points in interface testing that we are easy to ignore or need our attention:

1. Check whether the interface of the whole system is consistent with the effect picture (compared with the designed effect picture).

2. And check whether the interface style and design of all interfaces of the whole system are consistent.

3. Check if there are wrong words or inappropriate words in the interface.

4. Check whether the style of all the buttons on the interface is consistent and correct.

5. Check whether the operation of the interface is friendly and the user interaction is friendly.

6. Check whether all the buttons, drop-down boxes or navigation arrows in the interface respond correctly.

7. Check whether the link on the system has the correct link address and can jump correctly.

8. Check whether there are useless links in the system, that is, links are made in places that do not need to be made, and clicks do not jump properly or jump errors.

9. Check whether all the input boxes in the interface have been checked, for example, if the maximum limit character of the input box exceeds the maximum limit of the input box, the system will deal with it instead of reporting an error or other errors

10. Check whether the title or content in the interface will be wrapped or hidden when too much input, instead of interface dislocation.

Check the compatibility of the system in different browsers, check whether the page will be abnormal in different browsers, and whether the interface will be incompatible when the user resizes the browser window.

12. Check whether the font style and size used in the interface are consistent, and whether the format is uniform and accurate.

13. Check whether there are required colons after all fields, and see if the colons are unified Chinese colons or English colons, that is, whether the Chinese and English symbols are unified.

14. Check whether the pictures in the interface are displayed correctly, whether they are cut, whether they are stretched and deformed, and whether they are displayed completely.

Test method:

1. Static testing: static tests should be used for the layout, style, fonts, pictures and other tests related to the display of the user interface, such as the checklist test, which lists the items that must be passed by the checklist, and then make sure that each item is passed by observation.

2. Dynamic testing: dynamic testing should be used for each category of controls in the user interface, that is, a test case or checklist should be written to test the response of each button to see if it meets the conditions specified in the summary design. you can also test the display of the user interface in different environments.

Design method of Interface Test case

1. Form

How to test the form:

A, the size of the form should be appropriate, and the layout of the controls should be reasonable.

B, mobile form. Fast or slow mobile form, background and form itself must be refreshed correctly

C. Zoom the form, and the controls on the form should change with the size of the form.

D, display resolution. The display of the program must be tested at different resolutions.

When testing, we should also pay attention to whether the status bar is displayed correctly, whether the icon of the toolbar is valid, whether it is consistent with the display of the icon in the menu lazy, whether the error message is correct, no typos and clear, and so on.

2. Control

Test method:

A, form or control should have the same font and size

B. pay attention to full-width and half-width mixing

C, there is no mixture of Chinese and English.

3. Menu

Be aware of the following when testing:

Choose whether the menu can work properly and is consistent with the actual execution.

B. Is there any typos

C. Whether the shortcut keys are repeated.

D, whether the hotkey is repeated

E, whether the shortcut key and hotkey operation are effective

F, whether there is a mixture of Chinese and English

G, the menu should be context-related, for example, users with different permissions log in to an application, and users at different levels can see different levels of menus and use different levels of functions.

H, right mouse button shortcut menu.

4. Special attributes

A. the installation interface should have a company introduction or product introduction, with a company icon.

B, the main interface and most interfaces had better have a company icon.

C, select "help"-> "about" command, you should see the relevant copyright and product information.

Summary:

Nowadays, most people have the experience of using a browser to browse the web, although the user is not a professional, but the impression of the interface effect is very important. If you focus on testing in this area, it is important to verify that the application is easy to use.

Many people think that this is the least important part of testing, but on the contrary, it is very critical for customers who do not understand technology. You will understand that interface testing should be paid attention to!

Welcome to join the 51 software testing family, where you will get [latest industry information], [free test tool installation package], [software testing technology], [job interview skills]. 51 learn and grow with you! Looking forward to your joining: QQ Group: 755431660

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.