Operational characteristics distinction between web-side testing and mobile-side APP testing

I wrote it briefly before, this time I will talk about the characteristics of the two in detail. To

record bugs
　　
on the Web side, you can capture the bug pictures through the screenshots and QQ screenshots that come with the system. For the wrong places, you can use the logo that comes with the tool to show Emphasis mark.
　　
For mobile devices, you can use the screenshot tool that comes with your phone to take screenshots and then upload them to your computer. Individuals are generally used to installing the Windows version of WeChat and sending them to the PC through the file transfer assistant. There is also a more convenient way to connect the mobile phone to the computer with a data cable, configure the Android operating environment locally, download asm.jar, and run Java -jar asm.jar in cmd to synchronize the mobile phone screen in real time. Use the screenshot tool on the PC side to take screenshots directly. IOS can install itools on the PC, and the screen can be synchronized if necessary.
　　
Suggestions for recording bugs:
　　
The topic of bugs should be as concise as possible, and can be described in detail in the bug description. For bugs with more complicated operation steps, the operation steps should be written in detail. If necessary, attach relevant logs, record the test environment, mobile phone version, etc. The bugs that must be found and not must be found should also be explained in detail to reduce unnecessary communication costs.

Test environment
　　
The test environment on the Web side is often switched through hosts. The switchhosts tool can easily switch the required hosts, but the mobile terminal is more complicated to set up. The simpler way is to set the proxy on the computer and connect the proxy directly on the mobile phone. Note that the phone and computer must be connected to the same network.

Compatibility
　　
tests on the web side generally mainly use a browser, and when the system is basically stable, test the compatibility of the browser.
　　
However, for the mobile terminal, this method does not work, because the mobile terminal is mainly divided into Android and IOS, and the problems at these two ends are generally inconsistent. The consistent problems are mainly data problems. At this time, it is necessary to It is processed in the background, so when we test, we need to focus on testing both ends, and there will be no problem of focusing on testing one end first.

Characteristics of the
　　
mobile terminal Compared with the web terminal, the mobile terminal has many characteristics of its own:

There are many types of networks: There are various types of networks on the mobile terminal: wireless network, 2G, 3G, 4G, etc., the network is disconnected, the network speed is poor and The display of pages when switching between networks is very important for mobile terminals. In addition, under non-wifi, you also need to pay attention to the problem of network usage.

Interruption problem: There is a very important problem in mobile APP testing . Generally, the process of using the software is not long-term, and many interruptions may occur in the middle, such as calls, text messages, notifications, power failures, etc. The software needs special handling These special cases are the limitations of interrupting the test

screen : the display of pictures and text; whether the uploading of different picture sizes is normal; what is the effect when the pictures and text are displayed together.
　　
Operation area: The application on the web side is generally not limited by the screen, and it is more accurate to operate through the mouse. However, due to the small screen size of the mobile terminal, pages and buttons will be limited by the size of the screen. In addition, users operate with their fingers, whether some buttons, selection boxes, etc. are easy to click. When the positions of multiple clickable areas are close, click A slight deviation of the part may result in different results. In this case, whether the pre-set effect can be achieved.

Software startup and operation: The mobile APP starts, uninstalls, and upgrades several features, which are relatively common and important, such as what to do with the user's data during the upgrade, how to deal with the user's data after uninstallation, and uninstall and then install the user's login data. display etc.

Gestures: Another feature of the mobile terminal is that the mobile terminal has its own relatively simple gestures. Users can perform an operation through gestures, such as left swipe to delete, right swipe to return to the previous page, left and right swipe pictures, etc. The software needs to perform this gesture. adaptation.

Sharing: There are usually many apps installed on the mobile terminal. When the user places an order or the product has an activity, the user will share it. However, problems such as permissions and software existence during sharing require special handling and testing. In general APPs, some pages will be opened, allowing users to access without logging in, and some pages must require users to log in, mainly for these two pages with different permissions to share, and then enter this page through sharing to view the permissions. control is normal. Sharing is just a simple function. For an APP, there are many functions, and APP function testing is particularly important.

Synchronization of web and mobile terminal: whether the user's operation on the web terminal can be synchronized and displayed normally on the mobile terminal; the operation on the mobile terminal, the user logs in to the web account, whether the information is synchronized, etc.