As part of the Android Compatibility Program, Google provides smartphone OEMs with access to the Compatibility Test Suite (CTS). The suite includes a collection of more than two million test cases that OEMs use to spot bugs early in the smartphone development process so that users have a consistent app experience across different devices. However, CTS mostly consists of tests written by Android engineers with very little input from app developers. To give app developers a chance to share their “Unique perspective on real device compatibility issues,” Google has now introduced CTS-D.
CTS-D is a new CTS module that includes compatibility tests written by app developers. This already includes some of the tests contributed by the community, and Google is now inviting more developers to create and contribute test cases for those experiencing app compatibility issues. The company further notes: “We know that many of you have already built your own tests to verify compatibility on different devices. We look forward to working with you to bring those tests to AOSP.”
To submit a new test, you can file a proposal using this template before giving your test code to AOSP. Android team will then review Your submission to verify its eligibility. Currently, Google is inviting app developers to submit power management test cases.
At a minimum, Google says that if a device doesn’t pass the CTS-D test, developers can report the problem to the issue tracker and Google will “work” with a partner to resolve it.
Mishaal Rahman (@Mishaal Rahman) 23 June 2022
Along with app developers, Google is also “strong advice” Smartphone OEMs will use CTS-D to identify and mitigate issues. However, the company does not strictly require OEMs to run CTS-D tests to pass device certification. As a result, some OEMs cannot run CTS-D tests on their equipment. If this happens, app developers will have the option to file a report if a device does not pass the CTS-D test using this issue tracker template. Google says it will work with OEM partners to resolve this.
Source: Android Developers Blog
