CTS Introduction
I. INTRODUCTION of CTS
CTS Full name compatibility test suite Compatibility testing tool.
When electronic products have been developed and customized to their Android system, it is necessary to pass the latest CTS detection to ensure that standard Android apps can run on the platform.
CTS verification is required to submit the test report to Google, which has been certified by Android Market
Second, why do I need CTS test?
1, let the app provide a better user experience. Users can choose more apps that are right for their devices. Make apps more stable.
2. Let developers design more high-quality apps.
3, through the CTS device can run Android Market.
Third, how can I make my device compatible?
1. Match the Android Compatibility definition document, the documentation lists the hardware and software features of the compatibility device
2. CTS is an open source test framework for testing your device for compatibility with CTS testing.
3, submit the report, after testing CTS, the test results sent to [email protected]. You can also request access to Android Market
Iv. working principle of CTS
CTS Automated testing consists of two parts:
1. Run the test framework component on the PC. Primarily used to manage the execution of test cases
2. Run the test case on the device or simulator. These use cases are written in Java apk file
V. CTS process
1. Get CTS (source code compilation/website download)
2. Install and configure CTS.
3. Connect the device to the PC.
4, run CTS. The CTS installs the corresponding test case (APK file) on the device, runs it, logs the result of the run, and finally deletes the test case.
5. After all test cases have been executed, the system can be re-adjusted or optimized with reference to the test results. Then continue to run the CTS test.
6, after the test passed, the CTS generated results (that is, the result folder below the. zip file) and the device some additional information (such as: Screen captures) submitted to [email protected].
Vi. type of CTS test
The CTS consists of the following three levels:
1, the unit level. Test the code unit on the Android platform. For example, a class like Java.util.HashMap.
2, functional level. A more advanced test example that combines multiple APIs.
3, program level. Run the app to test all the APIs and Android services.
Future versions will also contain the following types:
1, strength test. Test the stability of the system under high CPU operation.
2, efficiency test. For example, the number of frames rendered per second.
Environment construction
First, the ADB environment variable configuration
' Vim ~/.BASHRC, add the following two sentences to the file header
Export SDK_ROOT=/HOME/XXX/SDK
Export Path=${sdk_root}/platform-tools:${sdk_root}/tools: $PATH
Second, compile CTS
SOURCE build/envsetup.sh
Make CTS
After the compilation is complete:
Build to Out/host/linux-x86/cts
Third, ADB connection equipment
1: All testing takes about 6 hours, we recommend using USB to connect adb
2: If it is only part of the test, you can select the network or USB
Four, device settings
1:settings->developeroptions-> the Enable USB debugging, Stay Awake, Allowmock Locations 3 options open
2:settings->security->device Administrators all options inside (this is set after the CTS starts testing, after the first reboot)
Five, test steps
Here are the complete test steps, some of which are shown in Out/host/linux-x86/cts/android-cts/tools/readme
CD Out/host/linux-x86/cts/android-cts/tools
./cts-tradefed
Run CTS--plan CTS
Start testing, such as:
Attention:
The device restarts several times during the test and does not interrupt the CTS Test window of the terminal
Vi. test Results
such as: Test complete
Results in the Cts/android-cts/repository/results directory
Some of the results are as below:
Android Performance Test CTS Chapter