7 major points of note for app functional testing

1. Running

1) After the app installs the test run, can open the software normally.

2) app open test, whether there is a progress prompt to load status.
3) The switch between the app pages is smooth and the logic is correct.
4) Registration
Same Form Editing page
User name Password length
Post-Registration Tips page
The front registration page and background Management page data is consistent
After registering, in the Background management page prompt
5) Login
Using a legitimate user login system
Whether the system allows multiple illegal logins, and whether there are times limit
Log in to the system using an account that is already logged in to correct processing
User name, password (password) error or missing fill in the login can
Deleted or modified users, the original user name login
Do not enter user password and duplicate point "OK/Cancel" button, whether to allow login
After landing, the login information on the page
There is a logout button on the page

Processing of logon Timeouts

2. Front and rear switch of the application
1) The app switches to the background and back to the app, checking to see if it stays on the last user interface.
2) The app switches to the background, then back to the app, check the function and application status is normal.
3) The app switch to the background, and then back to the foreground, notice whether the program crashes, functional status is normal, especially for switching back from the background to the foreground data has automatic updates.
4) Mobile phone lock screen after unlocking into the app note whether it will crash, functional status is normal, especially for switching back from the background to the foreground data has automatic updates.
5) When the app is in use, the phone comes in and then switches to the app, the function status is normal.
6) When the app is killed in the city, and then open App,app can normally start.
7) The prompt box must be processed, switch to the background, and then switch back, check whether the prompt box is still there, and sometimes the application will automatically skip the hint box defects.

8) for the data exchange of the page, each page must be the front and rear switch, lock screen test, this page is most prone to crash.

3. Free Login
Many apps offer a no-sign-on feature that automatically uses the app as soon as the app is turned on with the user's identity.
1) Consider the ability to enter the non-logon state normally without network conditions.
2) After the user login, to verify the user login information and data content is updated to ensure that the original user exit.
3) According to the existing rules of Mtop, an account is allowed to log on only one machine. Therefore, it is necessary to check the situation of one account login to multiple phones. The original mobile phone users need to be exited, give a friendly hint.
4) The app switches to the background and switches back to the foreground check.
5) switch to the background and switch back to the foreground test.
6) After the password change, check if there is a valid identity verification when the data exchange.
7) An application that supports automatic login checks that the system can log on successfully and that the data is operating correctly when the data is verified.

8) Check that the user is actively logged out, the next time you start the app, you should stay in the login screen.

4. Offline browsing
Many apps support offline browsing, where local clients cache part of the data for users to view.
1) Local data can be browsed in wireless network conditions.
2) When you exit the app and then open the app, you'll be able to navigate.
3) switch to the background and back to the front desk can be viewed normally.
4) lock screen and then unlock back to the application foreground can be viewed normally.

5) When the data on the server segment is updated, the corresponding prompt is given offline.

5.APP Update

1) There is an update prompt when the client has a new version.
2) When the version is a non-mandatory upgrade version, users can cancel the update, the old version can be used normally. The update prompt will still appear the next time the user launches the app.
3) Exit the client when the version is a mandatory upgrade, but the user does not make an update after the mandatory update is given. The next time you start the app, a mandatory upgrade prompt still appears.
4) If the client has a new version, the direct update check will update properly if the client is not deleted locally.
5) When the client has a new version, if the client is not deleted locally, check whether the updated client features are new versions.

6) When the client has a new version, if the client is not deleted locally, check if the file with the same name as the picture can be updated to the latest version normally. If the above cannot be updated successfully, also belong to the flaw.

6. Positioning, Camera services

1) app is useful to camera, when location service, need to pay attention to system version difference.
2) useful to the camera service place, need to carry out front and rear switch test, check whether the application is normal.
3) When testing the camera service, you need to test it with a real machine.

7.PUSH Test

1) Check that the push message is sent according to the specified business rule.
2) The user does not receive a push message when it checks that the message is not received.
3) If the user has set a time-out period, the user cannot receive push during the time-free period. During a non-intrusive time period, the user receives the push normally.
4) When the push message is for the logged-on user, it is necessary to check that the received push is consistent with the user's identity and that no errors are pushed over the other person's message. In general, only the last logged-on user on the phone is sent a message push.

5) test push, you need to use a real machine to test.

>> stamp, free download app automation test Tool testwriter~