Compatibility Test Suite (CTS) Framework User
Manual
Android 4.1 CTS r1
Open Handset Alliance
Google Confidential
Contents
1. Why be compatible?
2. How can I become compatible?
2.1. Comply with Android Compatibility Definition document
2.2. Pass the Compatibility Test Suite (CTS)
2.3. Submit report
3. How does the CTS work?
3.1. Workflow
3.2. Types of test cases
3.3. Areas Covered
4. Setting up and using the CTS
4.1. Configuring the CTS
4.2. Setting up your device
4.3. Using the CTS
4.4. Selecting CTS Plans
5. Interpreting the Test Results
6. Release Notes
6.1. General
6.2. Known Framework issues
6.3. Known Test issues
7. Appendix: CTS Console Command Reference
Google Confidential
1. Why be compatible?
1.
Give your users the best possible experience with the applications they run.
When a device is compatible with Android, users can choose from among many
high-quality applications. Applications that take full advantage of Android's
features are likely to perform best on compatible devices.
2.
Make it easy for developers to write top-quality applications for your device.
Developers want to streamline their applications for Android, and this is easiest for
them when they are writing for a predictable platform.
3.
Take advantage of the Android Market.
Compatible handsets can give users access to the Android Market.
Android compatibility is free, and it's easy.
Google Confidential
2. How can I become compatible?
2.1. Comply with Android Compatibility Definition document
To start, read the Android compatibility definition for the Android platform version
that you want. This document enumerates the software and the hardware features
in a compatible Android device. Except where noted, the features are all required
for Android compliance. To learn more about Android compatibility definition in
general, and to locate and download a particular definitions document, see the current
Compatibility Definition. Archived versions of older Compatibility Definitions may be
found on the Downloads page.
2.2. Pass the Compatibility Test Suite (CTS)
The Compatibility Test Suite (CTS) is a downloadable open-source testing harness that
you can use in any way you like as you develop your handset; for example, you could
use the CTS to do continuous self-testing during your development work. For more
about the CTS and the compatibility report that it generates, see the Compatibility Test
Suite page. For instructions on using the CTS, see the CTS User Guide.
2.3. Submit report
When you are ready to claim compatibility for your device, you can submit the CTS-
generated report to cts@android.com. When you submit a CTS report, you can also
request access to the Android Market.
* This is an early preview of CTS. The compatibility site and the service to certify your
compatibility reports are work in progress - we will update you when these are ready.
Google Confidential
3. How does the CTS work?
The CTS is an automated testing harness that includes two major software
components:
●
The CTS test harness runs on your desktop machine and manages test execution.
●
Individual test cases are executed on attached mobile devices or on an emulator.
The test cases are written in Java as JUnit tests and packaged as Android .apk
files to run on the actual device target.
3.1. Workflow
1.
Use the bundled CTS release or download the CTS from the Android Open
Source Project onto your desktop machine.
2.
Install and configure the CTS.
3.
Attach at least one device (or emulator) to your machine.
4.
Launch the CTS. The CTS test harness loads the test plan onto the attached
devices. For each test in the test harness:
○
The test harness pushes a .apk file to each device, executes the test
through instrumentation, and records test results.
○
The test harness removes the .apk file from each device.
Google Confidential
