Support HIDL's inter-package import and ref type

- Handle some corner cases
- Also use package name in driver callback wrapper function

Test: mma
Change-Id: I0f1f462fc697f430838843d6169bd82121baaefa
14 files changed
tree: d95a44e7e0dab4abf002aeb2ae93d8a08280d6d2
  1. agents/
  2. doc/
  3. drivers/
  4. hals/
  5. harnesses/
  6. proto/
  7. runners/
  8. script/
  9. specification/
  10. sysfuzzer/
  11. testcases/
  12. tools/
  13. utils/
  14. web/
  15. .gitignore
  16. __init__.py
  17. Android.bp
  18. Android.mk
  19. build-java.sh
  20. build-python.sh
  21. create-image.sh
  22. README.md
  23. run-gce.sh
  24. run-local.sh
  25. run-unittest.sh
  26. setup-gce.sh
  27. setup-local.sh
  28. setup.py
  29. vts.mk
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
  4. VTS Framework Developer Manual