Simple chat app Test

First, the outline
1. Functional Testing
2. Compatibility test
3. Weak network Testing
4. Stability Testing
5. Security Testing
6. Performance Testing
7.H5 Test

Second, the key test points:
(1) Functional testing
Verify the app's functions according to the software description or user requirements;
According to the needs, refining the app users use the scene, verify the function;
Verify the function according to relevant test standards;
According to the characteristics of the measured function points, a special method is used for testing;
During the testing process, even if the business or understanding the requirements of the error;
Use mind map to write and design test points.
Common functional defects:
function does not work (menus, buttons, links, controls, etc.);
Functional errors (inconsistent with expected results, calculation errors, display errors, etc.);
Missing functions (lack of menus, buttons, options, etc.);
After performing the function, the system is paralyzed (crashes, CPU shortage, ANR, etc.);
After performing the function, the current function cannot continue operation, etc.
Install (upgrade) and uninstall:
Whether it can be installed in different versions of Android (some software has a minimum version of the adaptation);
Whether it can operate normally after installation;
If the abnormal situation has the corresponding normal prompt;
If there are factors such as network, consider whether it is normal in the case of disconnection;
Installation process If there is a text message, alarm, telephone, power outage and other abnormal situation, whether the normal installation success.

Run:
After the installation is complete, whether it can open normally;
When normal use, whether there are operation guidance and loading tips;
Running speed, interface switch is smooth.

such as login function:
If the user name or password is wrong, you should have the correct reminder;
After the user exits the login, the next time the app is launched, it will be displayed as login screen;
If you log in automatically, open the page you want to display directly;
If there is a Web side of the app, update the data to synchronize the changes in the database.
If there is a mobile login to the mutual kick mechanism, the next time the abnormal login, the original user should have the correct reminder and so on.
Data is offline and cached, and in the case of no net, the cached data is displayed. After the network, the data should be updated in time.
Clear cache:
In the phone settings, you can clearly understand the current app's data and cache. (Clear Data > Clear cache)
In the process of running the app, after clearing the data, is there any exception to the program;
If you open it again, it will not go back.
(2) Network environment
Test the operation of the software in the case of 2g,3g,4g,wifi;
In the company intranet and outdoor external network to carry out testing;
Speed of the situation, whether the exchange of data can be successful, if the failure of how to prompt;
From a network to no network to have a network, the data can be normal reply.

(3) UI test
Ensure that users can use the software functions correctly, quickly and effectively through the interface;
Ensure that the app interface complies with company or industry standards, including user-friendliness, humanization, and operation.
(4) Abnormal test
Multiple app switching, cannot be forced to kill the process;
The app will still work after forcing the data to be emptied;
Long time to open the app, whether there will be a program exception, (especially maps, sweep code, positioning and other software)
After the network switch, whether it can respond normally.
(5) Compatibility test
The main points of view are:
Operating system version (minimum compatible);
screen resolution/size;
different mobile phone brands;
Android fragmentation problem, incurable diseases.
(6) Safety test
Permissions issue: For a permission that is not required to be acquired, make the development delete.
Store sensitive information in the database: The user's password, payment password or fingerprint and other key information, not only to encrypt the save, and in the user logoff, all of these sensitive information to be deleted.
Log information: In the development or debug version, will open the app's logging, but in the formal environment to shut down the log, otherwise prone to brute force to crack log information, access to user information.
(7) Performance test
How smoothly the app operates at different speeds;
Test the performance of the app operations database;
Stress testing;
Resource usage and consumption, and so on.

(8) Stability test
Summary of the ADB command:

The ADB command is an Android-generic debugging tool that can send shell commands, perform operations on your phone, install, uninstall, system upgrade, run shell commands, and more.
Listening Port: 5037
Get the status of a port: Netstat-ano | Findstr 5037

Windows Common commands:
D: Toggle D Drive
Cd.. Return to previous level directory
CD ABC enters the current directory
Dir lists the files and directories in the current directory
Mkdir Creating a Directory
Rd Delete Directory

Installing APK:ADB install . ( refers to: apk on the computer's storage directory and name)
Uninstall apk:adb Uninstall * * (** * refers to: APK package name)

Get all package names on the current phone: adb shell PM List Packages
(Third party's + system comes with)

Get the package name of all third parties on the current phone: adb shell PM List packages-3
(-3 means the third party's-s refers to the system's own)

Get information about the current device: ADB Get-serialno

Copy your computer's files to your phone: adb push * * ++++++
( * * refers to the path and name of the file stored on the computer. ++++++ refers to the directory that the target file is stored in the phone)

Copy your phone's files to your computer: ADB pull * *+++++++
(* * refers to the path and name that the file stores on the phone. ++++++ refers to saving files to the computer's storage directory)

Monkey detailed
The bottom of Android is the Linux system: View all folders: Ls-l

ADB Shell Monkey-p com.hrbb.directbanks-v-v-v-S 123--throttle--ignore-crashes--ignore-timeouts 20000

-P: Specify Package Name
-V: Primary log: The default value, which provides information such as startup hints, test completion, and final results.
-v-v: At least two v at work, typically two to three.
-S 123: Specify the same-s value, then send the same pseudo-random sequence two times
--throttle 300:300 milliseconds between events
--ignore-crashes: When the app encounters crash, continue with the operation. Until all operations are complete.
--ignore-timeouts: When the ANR is encountered and the system is unresponsive, continue with the operation until all operations are complete.
20000: The total number of executions of the event.

ADB Shell Monkey-p com.hrbb.directbanks-v-v-v-S 123--throttle--ignore-crashes--ignore-timeouts 20000 >E:/erro R.txt
(Save the log in the Error.txt file below the test folder under E-drive)

In the saved log, you can search for keywords, crash, error, ANR, and so on. Used to locate the bug that occurred in the analysis.

Simple chat app Test