In the exploration of daily work, we will simply summarize the points of attention on how to do app testing as follows.
01
run
1) After the app is installed, the trial run can be opened normally.
2) App opens to test, whether there is a progress prompt of loading status.
3) Whether the switching between App pages is smooth and the logic is correct. 4 )
Registration
Same as the form editing page
Length of username and password
Prompt page after registration Whether
the data on the front-end registration page and the back-end management page are consistent
After registration, the page prompts in the back-end management Illegal login, whether there is a limit on the number of times. Is it correct to use the logged-in account to log in to the system ? Can the user name, password (password) be wrong or missing ? Click the "OK/Cancel" button, whether to allow login After login, the login information on the page There is a logout button on the page
Handling of login timeout
02
Switching between the front and back of the application
1) Switch the App to the background, then go back to the App to check whether it stays on the last operation interface.
2) Switch the App to the background, and then return to the App to check whether the function and application status are normal.
3) When the app switches to the background and then returns to the foreground, pay attention to whether the program crashes and whether the functional status is normal, especially when the data is automatically updated when switching from the background to the foreground.
4) After the phone is locked and unlocked, enter the App to pay attention to whether it will crash and whether the functional status is normal, especially when the data is automatically updated from the background to the foreground.
5) When a phone call is interrupted during the use of the app, and then switch to the app, whether the functional status is normal.
6) After killing the App and entering the city, and then opening the App, can the App start normally.
7) After the prompt box that must be processed appears, switch to the background, switch back, and check whether the prompt box still exists. Sometimes there is a defect that the application automatically skips the prompt box.
8) For pages with data exchange, each page must be tested for front-to-background switching and screen lock, which is the most prone to crash.
03
No login
Many apps provide a login-free feature, which automatically uses the app as the last logged-in user when the app is opened.
1) Consider whether you can enter the login-free state normally when there is no network.
2) After switching users to log in, verify the user's login information and whether the data content is updated accordingly to ensure that the original user logs out.
3) According to the existing rules of Mtop, one account is only allowed to log in to one machine. Therefore, it is necessary to check the situation that one account is logged in to multiple mobile phones. The user in the original phone needs to be logged out and a friendly prompt is given.
4) App switches to the background, and then switches back to the foreground for verification.
5) Switch to the background, and then switch back to the foreground test.
6) After the password is changed, check whether the valid identity verification has been carried out when there is data exchange.
7) When an application that supports automatic login is performing data verification, check whether the system can automatically log in successfully and the data operation is correct.
8) After checking that the user actively logs out, the next time the app is launched, it should stay on the login interface.
04
Browse offline
Many applications will support offline browsing, that is, some data will be cached on the local client for users to view.
1) In the case of wireless network, you can browse local data.
2) You can browse normally when you exit the app and then open the app.
3) Switch to the background and then back to the foreground to browse normally.
4) After locking the screen and then unlocking it back to the foreground of the application, you can browse normally.
5) When the data of the server segment is updated, it will give a corresponding offline prompt.
05
App update
1) When the client has a new version, there is an update prompt.
2) When the version is a non-mandatory upgrade version, the user can cancel the update, and the old version can be used normally. When the user starts the app next time, the update prompt still appears.
3) When the version is a mandatory upgrade version, but the user does not update after the mandatory update is given, exit the client. The next time you start the app, the forced upgrade prompt still appears.
4) When the client has a new version, without deleting the client locally, directly update to check whether it can be updated normally.
5) When the client has a new version, without deleting the client locally, check whether the updated client function is a new version.
6) When the client has a new version, without deleting the client locally, check whether the resource file with the same name, such as the picture, can be updated to the latest version normally. If the above cannot be updated successfully, it is also a defect.
06
Positioning, camera services
1) When the App uses the camera and locates the service, you need to pay attention to the difference of the system version.
2) Where the camera service is useful, it is necessary to perform a switching test between the front and the background to check whether the application is normal.
3) When testing the camera service, you need to use a real machine for testing.
07
PUSH test
1) Check whether the Push message is sent according to the specified business rules.
2) When checking not to receive push messages, the user will not receive push messages.
3) If the user has set a do-not-disturb time period, check that the user cannot receive Push within the do-not-disturb time period. During the non-do-not-disturb time period, the user can receive Push normally.
4) When the Push message is for the logged-in user, it is necessary to check whether the received Push is consistent with the user's identity, and push other people's messages without error. Generally, only the last logged-in user on the mobile phone is pushed to the message.
5) When testing Push, you need to use a real machine for testing.