"Reprint" mobile internet app test flow and test point function test

AppFunctional Testing

According to the software description or user requirements to verify the implementation of the various features of the App , the following methods to implement and evaluate the functional testing process:

1) Use the time, place, object, behavior and background five elements or business analysis methods to analyze and refine The user usage scene of the App, compare the instructions or requirements, collate the internal, external and non-functional directly related requirements, build test points, and clear test standards, if the user needs are not clear standards to follow, you need to refer to industry or relevant international standards or guidelines.

2) According to the characteristics of the measured function points bowl out the corresponding type of test cases to cover them , such as, the place involved in the input needs to consider equivalence, boundary, negative, abnormal or illegal, scene rollback, association test and other test types to overwrite it.

3) keep track of the coverage of the test implementation and requirements input at all stages of the test implementation , and revise the business or demand comprehension errors in a timely manner.

1 Run

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)App Open Speed test, whether the speed is considerable.

4) Whether the switch between the APP pages is smooth and the logic is correct

5) Registration

--Same Form editing page
--User name password length
--Post-Registration Tips page
--The Front desk registration page and the Background Management page data is consistent
--after registration, in the Background management page prompt

6) Login

--Use a legitimate user login system.
--whether the system allows multiple illegal landings, and whether there are times limit.
-Use the logged-in account to log on to the system for proper handling.
--Use the Disabled account login system is correct processing.
--whether the user name, password (password) error or missing fill in the login.
-Deleted or modified users, the original user login.
--Do not enter the user password and user, repeat point (OK or Cancel button) is allowed to login.
-After landing, the landing information on the page.
--There is a logout button on the page.
--Processing of login timeouts.

7) Logout

--Write off the original module, the new module system can be handled correctly.
--Terminate the logout can return the original module, the original user.
--Write off the original user, the new user system can be handled correctly.
--Log off with an incorrect account number, password, and a disabled account with no permissions

2 front and rear switch for 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) app switch to the background, then back to the app, check the function and application status is normal, IOS4 and IOS5 version of the processing mechanism are different.

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 unlocking after entering 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, when the phone comes in and then switches to the app, is the function status normal?

6) When the app process is killed, the App,app can start normally.

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 crashes.

3 Free login

Many apps offer a login-free feature that automatically uses the app as soon as the app is turned on with the user's identity.

1) When the app has a login-free feature, you need to consider the iOS version differences.

2) Consider the ability to enter the non-logon state normally without network conditions.

3) After switching user login, to verify the user login information and data content is updated to ensure that the original user exit.

4) 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 that one account is logged in to multiple phones. The user in the original phone needs to be kicked out and given a friendly hint.

5) The app switches to the background, then back to the front of the check

6) switch to the background and switch back to the foreground test

7) After the password change, check if there is a valid identity verification of the data exchange

8) An application that supports automatic login checks to see if the system is automatically logged on and the data is operating correctly when the data is exchanged.

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

4 Data Update  

According to the application business rules, as well as the amount of data update, to determine the optimal data update scheme.

1) need to determine which areas need to provide manual refresh, which need to be automatically refreshed, where manual + automatic refresh is required.

2) You need to update the data to determine where to switch back from the background to the foreground.

3) According to the reasonable allocation of business, speed and traffic, determine which content needs to be updated in real time and which needs to be updated regularly.

4) Determine the processing logic of the data Presentation section, whether it is requested from the server or cached locally, so that the corresponding test can be targeted.

5) Check where there is data exchange, there are corresponding exception handling.

5 Offline browsing  

Many apps support offline browsing, where local clients cache part of the data for users to view.

1) can browse local data without network condition

2) When you exit the app and then open the app, you can browse

3) switch to the background and cut back to the front desk for normal browsing

4) lock screen and then unlocking back to the application foreground can be viewed normally

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

6 App updates

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) When the version is a forced upgrade, when the user does not make an update after the mandatory update is given, the client exits. 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 whether the file with the same name can be updated to the latest version properly. If the above cannot be updated successfully, also belong to the flaw.

7 positioning, Camera services  

1) app useful to camera, location service, need to pay attention to system version difference

2) useful to location services, camera services, the need for a front and rear switch test, check whether the application is normal.

3) If the location service is not turned on, use the location service and the friendly popup will allow setting the location prompt. When you are sure to allow the positioning to be enabled, you can automatically jump to the location settings to turn on location services.

4) Testing the positioning, camera services, you need to use the real machine for testing.

8 Time Test  

The client can set the phone's time zone and timing itself, so it needs to verify the impact of the setting on the app.

-- China is the East 8 District, so when the phone set time is not East 8, see where the time needs to be displayed, whether the time is displayed correctly, the application function is normal. Time generally need to be based on the server time and then converted to the corresponding time zone of the client to display, this user experience is better. For example, to publish a microblog on the server record is 10:00, when the Washington time is 22:00, when the client to browse, if the setting is Washington time, the display of the published time is 22:00, when the time is set back to the East 8 zone time, then the view is displayed as 10:00.

9 PUSH Test

1) Check whether the push message is sent according to the specified business rules

2) Check that the user is no longer receiving push when the push message is not accepted.

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, you need to check that the received push is consistent with the user's identity and that no error has been sent to 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.

"Reprint" mobile internet app test flow and test point function test