make sure common.methods.open of conventional HAL is remotely callable

Change-Id: I59ea03468dc3da35a5c8dea445977ef3dae284ea
20 files changed
tree: 87e6d119dbd245dfd2be632c18efb85b607b016e
  1. agents/
  2. hals/
  3. harnesses/
  4. images/
  5. runners/
  6. sysfuzzer/
  7. testcases/
  8. tools/
  9. utils/
  10. .gitignore
  11. __init__.py
  12. Android.mk
  13. build-python.sh
  14. create-image-angler.sh
  15. create-image-bullhead.sh
  16. create-image.sh
  17. README.md
  18. run-angler.sh
  19. run-gce.sh
  20. setup-angler.sh
  21. setup-bullhead.sh
  22. setup-gce.sh
  23. setup.py
  24. setup.sh
  25. vts.mk
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and testcases, designed to help Android SoC Vendors, Device Manufactures, OEMs, and other partners enhance the robustness, reliability, and compatibility of:

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

VTS has manily two types of test suites:

  • automated (e.g., fuzzing) and
  • structural (e.g., gTest) testing.

Everyone can download the VTS package from the AOSP website, and run the VTS tests in order to produce a VTS report, which can be submitted to the Android Partner Engineering to obtain a certificate.