Google seeks input from Android app developers on device compatibility issues

ByLance T. Lee

Jun 24, 2022

What do you want to know

  • Google’s CTS-D is a new test module to help developers identify compatibility issues with Android devices.
  • The CTS-D will allow application developers to contribute test cases for others to use.
  • Google hopes Android OEMs will use these tests to help identify issues more effectively.

Google presents CTS-D, a new module within the CTS (Compatibility Test Suite). It will be used by application developers and is open source under the Android Open Source Project (AOSP). The goal of the new module is to enable more effective communication between app developers, OEMs, and Google, while helping to resolve compatibility issues to ensure apps work consistently across devices.

CTS is already a crucial part of the company’s Android compatibility program, where smartphone OEMs test their devices during development to recognize bugs and fix them as soon as possible. Android engineers normally write these tests, and the CTS holds a collection of two million test cases to check the compatibility of Android devices.

CTS-D: How does that come into play?

Instead of Android engineers overseeing all compatibility testing, Google wants to hear what app developers have to say about compatibility issues, as they would naturally be more aware of their apps. This is where the new CTS-D test suite comes in, as the new module is primarily driven by app developers, Google notes in the Android Developer Blog.

Since app developers use the new module, they are allowed to create and contribute test cases to help report issues and check compatibility with top Android phones and other devices. Google notes that many app developers may have already created their own versions of app compatibility testing, and the company wants them to contribute all of their testing to AOSP. Integration can help these tests reach a fuller range of developers, which translates into helping OEMs and device developers identify and fix them as soon as possible.

Additionally, Google provides an issue tracking model where issues such as device failure can be reported so that Google can resolve them with partners. Google also advises OEMs to use CTS-D to identify and reduce problems more quickly, although they are not required to pass these tests.

Developers can bring their test codes to the CTS-D after submitting a test proposal in the aforementioned issue tracking template. Like CTS, CTS-D test cases must meet specific eligibility criteria, which are reviewed by the Android team. Right now, Google says it’s currently interested in adding more test cases to address Android’s power management.

The new strategy seems to be promising apps and their developers, who are always on the verge of creating and updating the best Android apps to run on the latest Android devices. Hopefully, this will ensure that everyone can enjoy the best version of apps on Android devices and operating systems like the upcoming Android 13.


Source link