build a data flow path to pass hwbinder service name from a py test case
to a target-side driver

Test: run vibrator and nfc hidl test
Bug: 33544423
Change-Id: I8e063eed679afb00e0a60cf75df27a49f86dd12d
19 files changed
tree: 2643c5e3be3e04ffe6bd1d4fcb3034dcfa40f45c
  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-angler.sh
  22. create-image-angler_treble.sh
  23. create-image-bullhead.sh
  24. create-image.sh
  25. README.md
  26. run-angler.sh
  27. run-gce.sh
  28. run-unittest.sh
  29. setup-angler.sh
  30. setup-angler_treble.sh
  31. setup-bullhead.sh
  32. setup-gce.sh
  33. setup.py
  34. setup.sh
  35. 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., fuzzing) and
  • structural (e.g., gTest) 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.