Summary of Android Test Methods

Due to the need of work, recently to test the Android client software, I learned the method of Android client test, and now I share it with you.

1. Android client testing can be divided into the following major categories:

1. Android Black Box Test Tool
1) Including its own monkey, Monkey is a command-line tool in Android, which can run in the simulator or actual equipment
2) robotium and appium, tools for automated testing of black boxes. The target application can be tested with source code or only APK. Provides API that imitates user behavior, such as clicking on a control and entering Text
Wait.
2. White box test. Android integrates JUnit framework in SDK. Therefore, you can develop Android white-box test code based on JUNIT framework
3. Android's test method is mostly similar to web's test method, except that there are one more special test scenarios, such as traversal test, story-driven, adaptation test, power test, weak network test, traffic test and so on
4. For compatibility testing, 1 can use virtual machines to ensure the compatibility between systems, but more needs to rely on real machine testing, because there is still a big gap between virtual machines and real machines.

2. Before starting the test task, you should first check whether each test resource is ready.

--Product functional requirements document;

--Product prototype drawing;

--Product renderings;

-Behavior statistical analysis definition document;

--Test equipment;

--Others.

3. The test of 3. APP is divided into many points, some of which are listed below:

1. Permission test of software. Such as networking, sending information, opening the camera and other operations.

2. Install and uninstall security. For example, whether the installation is correct or not, whether the uninstallation is clean, etc.

3. Data security. If the password will not be displayed in clear text, whether the password is easy to decrypt, etc.

4. Call security processing. If the software in the process of running, received a phone call, whether the software running state can be saved, and give priority to the phone.

5. UI test. Whether the software running renderings are the same as the design renderings 1.

6. Functional testing. According to the design idea, run the software and observe whether each function can be executed correctly.

7. Background switching. For example, after switching the running APP to the background, whether the page is still displayed for the current one when it is opened again.