Designed proto fields to support hidl_handle API from host side

Test: make vts -j
Changes:
* Added proto request and response message for hidl_handle.

Change-Id: Ide7c5a307c680c596ef8d81347e6bfb2221288ad
Merged-In: Ide7c5a307c680c596ef8d81347e6bfb2221288ad
(cherry picked from commit 0f458337140b6a7332bdffe1c06bc9bab73a8919)
7 files changed
tree: 8b163d3c4d1284fb02800a1e35739fa8095b8248
  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)