As part of the Android Compatibility Program, Google gives smartphone manufacturers access to a Compatibility Test Kit (CTS). The suite includes a collection of more than two million test cases that OEMs use to eliminate bugs early in the smartphone development process so that users get a consistent app experience across devices. However, CTS mostly includes tests written by Android engineers with little input from app developers. To give app developers a chance to share files “Unique insights into actual device compatibility issues,” Google has now introduced CTS-D.
CTS-D is a new CTS module that includes compatibility tests written by application developers. He. She It already consists of a few tests contributed by the communityNow, Google is inviting more developers to create and contribute test cases to identify application compatibility issues they encounter. As the company notes: “We know that many of you have already created your own tests to check compatibility on different devices. We want to work with you to bring these tests into AOSP.”
To submit a new test, you can make a suggestion using this form Before contributing your test code to AOSP. The Android team will then review your submission to verify eligibility. Currently, Google invites application developers to submit Energy management experimental cases.
At the very least, Google says that if a device does not pass CTS-D testing, developers can report the issue to the issue tracker and Google will work with the partner to resolve it.
– Mishaal Rahman 23 June 2022
Besides app developers, Google also “strongly recommended” Smartphone OEMs should use CTS-D to identify and mitigate problems. However, the company does not strictly require OEMs to take CTS-D tests to pass device certification. Thus, some OEMs may not conduct CTS-D tests on their devices. If so, app developers will have the option to report if the device does not pass the CTS-D test using This template is a case tracker. Google says it will then work with OEM partners to resolve it.
source: Android Developers Blog
[ad_2]
