Android App Test experience summary
Start:1. Start the Portal: The desktop starts normally, the most recent run starts, the All Programs list starts, and the lock screen shortcut starts 2. Other portals: Open the app from another program, opening the app from the outside as a file (if any) 3. Return: Returning from another program to the application being tested, the application being tested opens another application and starts from the desktop icon. Cross-Assembly required
Test。 4. Abnormal start: Start after crash, write file is forced to kill the process after the start, network request did not receive the package after the forced kill process and then start, network timeout when the start (need to have time-out mechanism) function Introduction, guide diagram, traffic hint, etc.: 1 new Installation program first start, there will be some initialization, or the box hint , when the external open, such as third-party open (usually do not calculate the first start), then start the program, check whether there are any actions.
Permissions:1 when certain permissions are prohibited by the security software or the system, whether it can be used properly, need to pay attention to the rights: microphone/Camera/location/SMS and other rights-_luguo 2 in the compatibility test, you need to pay special attention to the more strict rights management ROM, such as Meizu in the camera and other permissions as the default off 3 Third-party security software when the box request prohibit permissions, when selected, will affect the application of the normal process file error 1 Using the wrong file type (but with the correct suffix name), instead of the file used by the test application 2 adb push files uploaded from the PC to the device if there is a Chinese name, will generate an error file, The application under test needs to adapt to this error condition
screen Rotation:1 Confirm which interface is required to allow horizontal screen or prohibit horizontal screen of 2 to lock the screen as a vertical screen or horizontal screen, in a few interface jump, the interface is normal 3 when the horizontal screen, whether the horizontal screen is adapted
Flow:1 The first time that the app's traffic is up to 2 when there are many pictures in the main interface, whether the image file size and display effect balance 3 when you need to use large network traffic (load big picture, video play buffer, download update package), show the current speed or progress, more friendly cache for users (/ sdcard/data/com.your.package/cache/): 1. The cache will be removed after uninstallation, where there are no files to delete (download files, user profiles) 2. Cache is easily
the
Mobile PhoneGuardian, cheetah cleanup master, etc. clean up and check if the folder has the appropriate files
Normal Interrupt:1. Perform the lock screen operation on all interfaces, and observe if it is running 2 after unlocking. Perform a long-time lock screen operation on all interfaces, and observe if the operation is functioning 3 after unlocking. At all interfaces, and all processes, press the home key to cut the background, and then cut back to see if the normal 4. In all loading processes, press the back key 5. In all loading processes, press the home key 6. The interface toggles the animation by pressing the back key 7 multiple times. Normal Click Action, try to press two times 8 quickly. Rear camera and front camera cannot be started simultaneously, rear camera boot also includes turn on flash (compatibility with flashlight class app) 9. Check the keyboard expansion and the timing of the collection, and home, back, lock screen combination test 10. After booting from a third party, the home button back to the desktop, and then open the application from the desktop, the display is correct (should be determined to display a third-party boot interface, or display the program normal start interface, the former such as the latter, such as QQ)
Abnormal interrupts: 1. Restart 2 after power off. When the interface crashes unexpectedly, the interface can be restarted and revert to state 3 before the crash. After the call is over, the application interface 4 is returned. In some special cases, after the call,
MovingThe network will be cut off.
User experience:1. Use the main feature of the application for the most discerning and unreasonable user perspective 2. Whether each action has feedback 3. Each button has a pressed state of 4. When the interface has a return button, back will perform the same operation 5. If the picture requires a network pull, or no picture, is there a default picture instead of 6. Turn on developer options, tick show layout boundaries, check that the clickable range of each button is reasonable
Multi-lingual:1. Language habits in other languages (e.g. traditional) 2. English note plural 3. In multiple languages, you need to check the copy shown in the image (if the function is booted, boot map) 4. Consistency. (On the one hand, the consistency of the point of reference, on the one hand if there is a series of application sharing function of the copy also need to be consistent) 5. If you downloaded a file in simplified or created a shortcut or made a purchase, switch languages immediately to do the same action 6. Check the English language of the cut and break is correct 7. If the text length is inconsistent, the UI interface will fit properly
"Tool" Android Application Test Experience Summary
