Hey there, let's break down your questions about Android Automotive CTS modifications and extensions clearly, based on official compatibility rules and industry best practices:

1. 是否允许OEM扩展或修改官方CTS测试用例？ #

Short answer: You can't modify official CTS tests, but you can add your own custom tests for device-specific features.

Google strictly prohibits OEMs from modifying official CTS (Compatibility Test Suite) test cases for Android Automotive. The core purpose of CTS is to enforce a unified compatibility standard across all Android devices—tweaking official tests would break this consistency, and could even result in failing Google's compatibility certification.

That said, there's no restriction on creating custom test suites to cover your device-specific changes or extensions; this is actually encouraged to ensure your unique features work as intended.

2. 相关指南文档（针对自定义扩展测试） #

Since modifying official CTS isn't allowed, there's no documentation for that scenario. But for building custom tests to cover extended functionality, you can refer to these official resources:

• Android Automotive Compatibility Definition Document (CDD): This outlines compatibility boundaries and provides guidance on what OEMs can customize, plus baseline requirements for any custom test suites you build.
• Android Test Development Docs: These cover how to build custom tests using frameworks like AndroidJUnitRunner or the CTS test framework, ensuring your tests align with Android's testing standards while validating your device-specific changes.

3. Google推荐的扩展功能覆盖方案 #

To validate your device-specific extensions without modifying official CTS, Google recommends these practical approaches:

• Build Device-Specific Tests (DSTs): Create your own dedicated test suite focused on unique hardware integrations (like custom in-car peripherals) or software customizations (like tailored cockpit UI workflows). These tests are maintained and executed by your team independently of official CTS.
• Extend CTS Verifier: CTS Verifier is a manual/context-dependent supplement to CTS. You can add custom test cases here to cover scenarios that require physical interaction or specific hardware setups unique to your automotive device.
• Leverage Partner Test Suites (if applicable): If you're a Google partner, you can access the Partner Test Suite (PTS) or collaborate with Google to define additional tests for niche automotive use cases that aren't covered by standard CTS.

All these approaches let you validate your custom features while keeping official CTS intact to maintain compatibility certification eligibility.

备注：内容来源于stack exchange，提问作者Mani Vannan