Note App seven points of functional testing
Groping their daily work, we will pay attention to how well the app to test a simple point comes down to the following.
Weak network testing, compatibility testing, UI testing, interrupted test,
01
run
1) Test operation App After installation is complete, the software can be opened normally.
2) App open the test, whether there is progress prompted the loaded state.
3) App Switching between pages is smooth, the logic is correct.
4) Sign up
with a form edit page
user name password length
prompt registration page after the
front desk registration page and back page of data management is consistent
registration, in the background management tips page
5) sign in
using a valid user login system
whether the system allows for multiple illegal login, if there are number of restrictions
account login system has logged correctly handle
user name, password (password) can log in error or is missing
deleted or modified user, the original user name login
without entering a password and repeat "OK / cancel" button, whether to allow login
after login, the login page
page there logout button
Login process timed out
02
Before and after application of a switching station
1) App switch to the background, and then back to the App, check if staying at a user interface.
2) App switch to the background, and then back to the App, and checking whether the application state is normal.
3) App switch to the background, when returned to the forefront, pay attention to whether the program crashes, whether the function status is normal, especially for switch back to the foreground from the background data when there is an automatic update.
4) after unlocking the phone lock screen will crash into the App pay attention to whether, if the normal functional status, especially for switching back to the foreground from the background data when there is updated automatically.
5) When using the App during a call comes in to interrupt and then switch App, whether normal functional status.
6) After the killing App into the city, and then open the App, App can start properly.
After 7) prompt box must be processed is switched to the background, and then switch back to check whether the prompt box there, sometimes the application automatically skip the prompt box defects occur.
8) for the exchange of data page, each page must be carried out before and after the switching station, lock screen test, the most prone to collapse this page.
03
Free landing
Many applications offer free sign-on function, user identity when the application is turned on automatically over time you log in to use App.
1) can normally logged into the free network without considering the circumstances.
2) after switching user login, to verify whether the user logon information and data content updated to ensure that the original user exits.
3) According to the existing rules Mtop, a login account only one machine. Therefore, the need to examine the case of a multiple account login mobile phone. Original cell phone users need to be quit, give prompt and friendly.
4) App switch to the background, switch back to the front desk check in.
5) switch to the background, and then switch back to the front desk of the test.
After 6) password replacement, check whether or not effectively verify the identity of the data exchange.
7) Support application automatic data validation during login, check whether the system can automatically log in successfully and data manipulation correct.
After 8) checks the user actively Log, next time you start App, should stay in the login screen.
04
Offline browsing
Many applications will support offline browsing, that is part of the local client caches data for users to view.
1) you can browse the local data in a wireless network conditions.
2) When you exit and then turn App App can browse normally.
3) switch to the background and then back to the front desk to see properly.
4) to unlock the lock screen and then back to the foreground application can browse normally.
5) When the data server segment prompted an update to give back offline.
05
App Updates
1) When a client has a new version, an update prompt.
2) When the non-mandatory version upgrade, users can cancel the update, the old version can be used normally. User next time you start App, still appears the update prompt.
3) When the version is mandatory upgrade version, but do not give force the user to update the update, quit the client. The next time you start the App, still appears mandatory upgrade prompt.
4) When a new version of the client, in the case of local does not remove client updates directly to check whether the normal updates.
5) When a new version of the client, in case of a local not remove the client, the client function after checking whether the update is a new version.
6) When a new version of the client, in the case does not remove local clients, check the resource file with the same name as the normal picture is updated to the latest version. If this is not successful update, it is a fault.
06
Positioning the camera service
When 1) App is useful to the camera, location services, you need to pay attention to differences in system version.
2) is useful to place a camera service, before and after the test need to switch stations to check whether the application is normal.
3) When the test camera service, we need a real machine tests.
07
PUSH test
1) Check whether the Push message transmitted according to the specified business rules.
2) Check the push message is not received, the user is not receiving the Push message.
3) If the user sets a time period of DND, DND inspection period, the user can not receive Push. In the non-disturb-free period, users can normally receive Push.
4) When the Push message is for user login time, you need to check the received Push and user identity are consistent, no error will be someone else's message push over. Under normal circumstances, only the last logged-on user on a phone message push.
5) testing Push, we need real machine test.