Android Application Functional Testing Strategy

Verify the implementation of each function of the App according to the software description or user requirements, and use the following methods to implement and evaluate the functional testing process:

1) Use the five elements of time, place, object, behavior and background or business analysis to analyze and refine the user usage scenarios of the App , Compare instructions or requirements, sort out internal, external and non-functional requirements directly related, build test points, and clarify test standards. If there is no clear standard to follow in user requirements, you need to refer to industry or relevant international standards or guidelines.

2) List the corresponding types of test cases to cover them according to the characteristics of the tested function points, such as; where input is involved, test types such as equivalence, boundary, negative, abnormal or illegal, scenario rollback, and association testing need to be considered overwrite it. 

3) Track the coverage of test implementation and requirement input at each stage of test implementation, and correct business or demand understanding errors in time.


1 Run

1) After the software installation is completed, the software can be opened normally.

2) App opens to test, whether there is a progress prompt of loading status.

3) App opens the speed test to see if the speed is considerable.

4) Whether the switching between App pages is smooth and the logic is correct

2 Registration

--same form editing page
--Username and password length
--Prompt page after
registration-- Whether the data on the front-end registration page and the back-end management page are consistent
--Register After that, the page prompts

3 login in the background management

--use a legitimate user to log in to the system.
-- Whether the system allows multiple illegal logins, and whether there is a limit on the number of times.
-- Whether logging in to the system with an already logged-in account is handled correctly.
-- Whether logging into the system with a disabled account is handled correctly.
-- Whether the user name and password (password) are wrong or omitted to log in.
-- The deleted or modified user, the original user logs in.
-- Do not enter the user password and user, repeat the point (OK or Cancel button) to allow login.
-- After logging in, the login information on the page.
-- There is a logout button on the page.
-- Handling of login timeout.

4 Logout

-- log out the original module, whether the new module system can be handled correctly.
-- Can you return to the original module and the original user after terminating the logout.
-- Log out the original user, whether the new user system can handle it correctly.
-- Use the wrong account, password, disabled account without permission to


log

out

2) Switch the APP to the background, and then return to the app to check whether the function and application status are normal. The processing mechanism of the IOS4 and IOS5 versions is different. 

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) Enter the app after the phone locks and unlocks the screen, 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) Switch to the app when a phone call is interrupted during the use of the app, whether the functional status is normal 

6) When the app process is killed, and the app is restarted, whether the app can be started normally. 

7) After the prompt box that must be processed appears, switch to the background, and then switch back to 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 switching between front and back and locking the screen. This kind of page is most prone to crash.

6 Data update 

The optimal data update scheme is determined according to the applied business rules and the amount of data update. 

1) It is necessary to determine which places need to provide manual refresh, which places need automatic refresh, and which places need manual + automatic refresh. 

2) Determine where data updates are required when switching from the background to the foreground. 

3) According to the reasonable distribution 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 display part, whether it is requested from the server every time, or cached locally, so that the corresponding tests can be carried out in a targeted manner. 

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

7 App update

1) When the client has a new version, there will be 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. The user will still be prompted for an update the next time they launch the app. 

3) When the version is a mandatory upgrade version, when 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 there is a new version of the client, without deleting the client locally, check whether the file with the same name as the resource, such as the picture, can be updated to the latest version normally. If the above cannot be updated successfully, it is also a defect. 



TestBird