Overview of the Compatibility program for the official Android CTS document

Compatibility Scenario Overview

Android's compatibility program makes it easy for Android phone manufacturers to develop compatible Android devices (Heaven Zhuhai Steering Note: What is compatible?). is to be compatible with the standard Google provides Android system can support the features, in case the handset manufacturer of open-source Android system modified beyond recognition, the developer development of the application is not installed, so the CTS to require mobile phone development must be tested on Google Play).

programme Objectives The Android Compatibility program takes into account the interests of all groups in the Android community, including users, developers and mobile phone manufacturers. These groups depend on each other, and the user wants to choose a wide range of mobile phone types and excellent applications, and the developers of good applications will be inspired by a broad market to develop more excellent applications, as their applications can reach the users of different types of mobile phones through this vast market. , and equipment manufacturers rely on these wide range of excellent applications to enhance the value of their products to users. (Heaven Zhuhai Branch rudder Note: In fact, the whole paragraph of the meaning of Google is to express my Google Play is a very powerful application market. Your Android device maker device wants to make money, think more developers can develop the right model for your application, want more users to use your phone, then you will use my Google Play, and you want to use my Google Play, then you castrated modified Android operating system must meet certain rules, Otherwise the user on my Google Play downloaded an application to your hands even if you can not use it for everyone is not good.

Our aim is to be designed for the benefit of the following people:

• provide application developers with a consistent application development environment and hardware environment : Without a compatibility standard, various devices will be varied, and developers will have to develop different versions of the application for each of the different devices. The compatibility scheme takes the form of a set of pre-defined APIs and capabilities (Heaven Zhuhai Steering Note: Capabilities can be understood as some of the features of a mobile phone) to provide a precise definition of what developers expect from a compatible device to be available. Developers can then use this information to make a good decision about how to design their application, and they are confident that the apps they develop can run well on any compatible device.

• provide a consistent app experience for consumers : If an app works well on a compatibility device, it should work well on all compatible devices with the Android version. A variety of Android devices vary in both hardware and software features, so this compatibility program provides tools to develop corresponding filtering capabilities for a variety of application distribution platforms, such as Google Player. This means that users will only see apps that their phones can run on the distribution platform.

• enabling device manufacturers to be compatible while still being unique : The Android Compatibility program is concerned with whether the Android system installed on the device can run well with third-party applications (Heaven Zhuhai Steering Note: In addition to the manufacturer's own application of third-party applications), This allows device manufacturers to provide a great deal of flexibility in how to create a unique and distinctive device while considering compatibility (Heaven Zhuhai Branch rudder note: Because handset manufacturers only need to be sure to meet the compatibility of Android, then you can do anything else on the device)

• additional costs associated with minimizing compatibility : Ensuring device compatibility is an easy and inexpensive task for equipment manufacturers. The Android Compatibility program provides tools that are free, open source, and downloadable. It is designed to allow equipment manufacturers to conduct continuous self-tests in the development of equipment so that equipment manufacturers can eliminate the additional costs associated with the development process changes or the delivery of equipment to third-party organizations for compatibility testing. At the same time, the Android compatibility program does not require any certification, so no corresponding fees and bills will be generated.

The Android Compatibility program consists of the following 3 key components:

• Source code in the Android software stack
• Compatibility definition document (CDD), which represents the "policy" definition for Android compatibility
• Compatibility test suite (CTS), which represents the "mechanism" for Android compatibility

Just as different versions of the Android platform will separate different branches from the source tree, different versions of CTS and CDD will have different branches (Heaven Zhuhai Branch rudder Note: Different versions of the Android system will have the corresponding version of the CTS and CDD corresponding). The cdd,cts and the source code described above, together with your own hardware and software customizations as provided by the handset manufacturer, are everything you need to create a compatibility device.

Compatibility definition document (CDD)

Every time an Android OS platform is released, a detailed CDD document is provided that represents the "policy" definition for Android compatibility.

In some cases, including the CTS, there is no test suite that can be all-in-one for exhaustive automated testing of all compatibility aspects. For example, there is a test in the CTS that examines the correct rendering and correct behavior of the OpenGL graphics library APIs on the screen, But no software test can verify that the corresponding graphics are actually rendered on the screen (Heaven Zhuhai Branch Rudder Note: The test case including the CTS is just a call to OpenGL API, and the test is not able to detect whether the screen has the corresponding graphics, can only be observed by the naked eye. This is what is known in the software testing industry is not all features can be implemented test automation. More generally, it is impossible to test the functionality of hardware rendering (using test tools), such as testing the key physical keyboard (if available), screen density, Wi-Fi hardware features, Bluetooth hardware features.

The role of CDD is to define and clarify specific requirements and to eliminate ambiguous ambiguities. CDD doesn't try to be all-encompassing, because Android itself is an open-source code collection, and the code itself is a full-fledged "documentation" of the Android platform and the APIs it provides (Heaven Zhuhai Steering Note: It should be clear that you know something about agile development and refactoring--to document it, Good code is the best document). CDD acts as a "hub" role, (bringing in the need for compatibility) to redistribute references to other corresponding content (such as the SDK API documentation), which provides a framework that the Android source code will use, so that the system will naturally become a compatible system. ( Heaven Zhuhai Branch Rudder Note: This paragraph should have a better way of translation, if crossing some please provide, I will selectively adopt )

If you want to create a compatibility device in an established Android version, start by downloading the version of the Android source code, and then carefully read the CDD documentation for that version of the source code and follow its guidelines. For additional information, please see the most recent CDD documentation.

Compatibility test Suite

CTS is a free, commercial-grade test suite that is available for download . The CTS represents the "mechanism" for Android compatibility.

CTS is a device that runs on your desktop system to drive connections to a desktop system host or a simulator to run the appropriate test case (script). CTS is a set of unit tests that are designed to allow us to integrate into our daily work processes (for example, by integrating into our continuous Integration System build system) to help engineers build an Android device system. It is meant to be exposed in the early stages of incompatibility, to ensure that the device is always compatible throughout the development process of the Android device system.

Compatibility test Suite Validator

The Compatibility Test suite Validator (CTS Validator) is an accessory feature of the CTS (Heaven Zhuhai: Actually an apk), which can be downloaded here. The CTS Validator provides APIs and functional tests (e.g., audio quality, accelerometer, etc.) that cannot be completed with interactive actions such as no user input

For more information about CTS, please inquire about CTS.

make/Translator : Heaven Zhuhai Branch Rudder

knowledge sharing public number :Techgogogo

CSDN: Http://blog.csdn.net/zhubaitian

Overview of the Compatibility program for the official Android CTS document