Shulou(Shulou.com)05/31 Report--

The content of this article mainly focuses on how to analyze the APP test and process. The content of the article is clear and well-organized. It is very suitable for beginners to learn and is worth reading. Interested friends can follow the editor to read together. I hope you can get something through this article!

In the current work, testing App will involve the following aspects: client, Mini Program, H6 page, etc., which look different but quite different.

Click to add picture description (60 words maximum)

1. Functional module testing: in fact, the most important thing in functional module testing is to examine the tester's ability of logical thinking and understanding of requirements, as well as the interaction of some pages and the consideration of input and output, etc., so the above three are in common. there's not much difference.

2. Rights management:

1) similarities: you need to consider whether permissions are allowed or not; you need to test more pages that do not have system permissions.

2) differences: when testing App, you need to consider whether users can access mobile communications, photo albums, cameras, storage space and other permissions, and what will happen when the permissions are turned off. Whether Mini Program needs Wechat authorization, whether it needs to be re-authorized after switching login accounts, etc. H6 pages generally consider whether you can enter the page without starting from the login entrance.

For example, a common mobile phone permission test: we will give up a lot of permissions when we run the software for the first time, so what will happen if we turn off the permissions and then open the application?

3, compatibility testing: general companies will provide App users to use more models for testing, generally App commonly used are: Android (Huawei, oppo, Xiaomi, etc.), IOS (iphoneX, iphone6, ipad, etc.), so many mobile phone models, the display of the page may have errors, some pictures or dynamic effects will be completely different, this is very necessary to consider, poor user experience is also a bug, ! In particular, the problem of bangs should be reminded, which is quite common. Mini Program mainly considers the compatibility of different Wechat versions, resolution, compatibility of QR codes (whether the client's QR code sharing, Mini Program's QR code sharing, etc., are displayed correctly, successful recognition, etc.), whether the H5 page is displayed correctly when opened by different browsers.

4. Interactivity: when testing, we have to test from the user's point of view, and those with bad experience can also communicate with the product, such as how to switch pages, dynamically exchange effects, return to the next level, interactive prompts, and so on.

5. Network situation: network delay (network status can be modified with packet grabbing software), network wifi/4g/3g/ no network / flight mode, no network to network / network to no network handover. Click the button when you are disconnected, and click again to view the effect after connecting to the network.

For example: disable wifi and data traffic or enable flight mode after logging in to the application, check if there is a network exception on the page, and refresh the page to see if it displays normally after the network is restored.

6. Performance testing: performance problems are common on App, such as white screen, flashback of resource occupancy, long page loading time, stutter, long login time for the first time, and so on. Performance testers will conduct performance tests based on application response time, memory occupancy, cpu occupancy, power consumption, traffic, and so on. It is understood that there are many performance problems with Android machines in Mini Program.

7. Caching issues: App and Mini Program consider caching more often. Mini Program can have a maximum of 10MB of local cache, so what is the cache for? Improve the fluency of the page, do not have to request data from the server again, reduce the server resource space, common cache problems: forced exit when caching is clear, system settings clear cache, etc.

8. Memory related: mainly tests whether the mobile phone's memory space is full, and whether many memory-consuming app are abnormal to this system (for App)

9. Special operations: of course, some special user actions should also be considered. For example, whether long pressing the picture can save the picture, whether the page can be scanned left and right, whether the page can be requested twice in a row (the limit is limited to one request), whether the page data will slide up and down when loading (the problem of flickering often occurs), whether the picture can continue to slide when sliding to the last page, clicking on the download situation when prompted to download the application in the H6 or Mini Program page, exiting the current process when opening, and so on. Too much, there is no coquettish operation you can't think of, this is what a test should do, !

10. Storage processing: (app) whether the storage space is full, whether the installation is successful, whether the storage space is full, whether the application can be opened; whether the user will be prompted when the memory is full when using the program; whether cache files will appear when saving pictures, whether the downloaded files and other information will be correctly stored in the mobile phone.

11. Push / pop-up messages: Mini Program push messages are messages from Mini Program Assistant, and App is the form of message push. Pay attention to whether the push message set at the backend is prompted correctly, click to check whether the push message enters the application (whether clicking the pop-up window will affect the current application), whether the push message is sent regularly or triggered, and so on. What is the trigger condition of the pop-up window, how long the pop-up window shows, and whether there will be a mask (whether the mask disappears when canceled, the case of clicking on the mask, etc.)

Mini Program message push:

12. Small details: other issues related to the hardware of the phone itself, such as power (whether you can use a camera when the power is low, etc.), messages, phone calls, etc., should be paid attention to.

Thank you for your reading. I believe you have some understanding of "how to analyze APP testing and process". Go ahead and practice it. If you want to know more about it, you can follow the website! The editor will continue to bring you better articles!

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.