1, phenomenon: when the user logs download the application initialization data, download speed is too slow process due to click Cancel and log in again, the data initialization is complete
duplicate after, resulting in inconsistent data.
The reason: data download, the download fails, the data is not rolled back, re-download after suspension, appear duplication of data
Solution: Transaction data download logic, the download fails, use a local database for data rollback.
2, phenomenon: the user clicks to upload data, network data upload process is weak and unstable, and upload the data automatically triggered based networking status, leading to
emergence of duplicate data is written, the formation of dirty data
The reason: the data upload process, due to the failure retransmission mechanism, there will be two consecutive write operations, and without making unique identification process
Solution: According to the characteristics of the dirty data may result in local, through key fields, such as creation time, key-value and other values
generated hash keys, uniqueness of the recording mark, i.e., data write, check hash key is present, If it does exist, this duplicate data discarded.
3, phenomenon: in the weak network environment, the user enters a user name and password and click login, use the link timeout returns user name and password error.
Cause: After the connection timeout weak network environment, the network service logic processing according to the intensity, causing the return timeout exception.
Solution: After a weak network connection timeout, the application checks whether there is a local database user login information, if there is immediate access local user
information to log on.
4, phenomenon: in the weak network environment, users enter a user name and password click login, the login process application crashes and flash back.
The reason: weak network environment data download times out, load data rely heavily loaded later asynchronous. Data have not had time to return the application to jump
to the next activity, leading to a crash.
Solutions: a robust data loading process, the download status flag data loading interface background, dependent on the data download is complete, then the page
surface jump.
5, the phenomenon: weak network environment, the user requests a page in response to a long time, waiting for the process, part of the controls on the page can still operate,
when the user clicks the control, application of flash back phenomenon occurs;
Cause: no data loading processes is determined, a controlled direct exposure control, when the control data dependent operation occurs, the data is not
done before the processing returns compatible.
Solution: In the data loading process, the external exposure controls settings page is "inoperable" when the data is loaded and then release.
6, phenomenon: in the weak network environment, users first enter the search keywords do not get a response, enter new keywords again and send the request
and wait for the search results are returned, before the current results of keyword search results page is refreshed coverage
Cause: after the request to return the intermediate slow display the final results, the data to be returned before the request is not processed.
Solution: asynchronous request unfinished task cancel.
In summary therefore, a test for the mobile APP, functionality, performance, stability, exception handling characteristics of the scene to summarize several dimensions, the test master network weak
to be concentrated in the scene as follows: 2G / 3G / 4G wifi- mobile network handover, etc. .
Bloggers welcome collection site 591q.cn