Switch vts-hal-adapter to cts-based plan.

* Add VtsHalAdapterModuleController to skip the test module if the
targeting hal is not available.
* Split cts-base.xml to cts-base-common.xml (contain all the cts plan
configure) and cts-base.xml (contains the basic test modules for cts
tests)
* Update VtsHalAdapterPreparer to only extend TargetPreparer.
* Update vts-hal-adpater to uss cts-base-common

Bug: 76152041
Test: make vts
      vts-tradefed run vts-hal-adapter -m VtsHalCameraDeviceV3_3Adapter

Merged-In: I32e2770665b9e4546931e86a528b9315f2dd5f78
Change-Id: I32e2770665b9e4546931e86a528b9315f2dd5f78
(cherry picked from commit bd9d356184b6939dbb185821131156c58a7ff3b4)
7 files changed
tree: 34696dda62b2873a19d6632353f002e139e7beda
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. proto/
  8. runners/
  9. script/
  10. specification/
  11. testcases/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitignore
  16. __init__.py
  17. Android.bp
  18. OWNERS
  19. PREUPLOAD.cfg
  20. README.md
  21. setup.py
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:

  • the Android system (e.g., Core HALs and libraries) and
  • low-level system software (e.g., kernel, module, and firmware).

VTS has mainly two types of test suites:

  • automated (e.g., record-and-replay and fuzzing) and
  • structural (e.g., gTest and host-driven python) testing.

While the VTS framework and test cases are designed for userdebug or eng build devices, some test cases can be run on user build devices using its app namely, VTS Agent App.

Table of Contents

  1. VTS User Manual
  2. Where to find VTS test cases
  3. VTS Test Developer Manual (Codelab)