add parent dir name(s) to config file path (to run in the platform test lab).

Change-Id: I467dec4a6b7251c1883fc4d3eed540c23e5a38bf
1 file changed
tree: 787c7a576cc6cc9cfcfbbcce4f508c148e2d408a
  1. agents/
  2. drivers/
  3. hals/
  4. harnesses/
  5. images/
  6. proto/
  7. runners/
  8. specification/
  9. sysfuzzer/
  10. testcases/
  11. tools/
  12. utils/
  13. web/
  14. .gitignore
  15. __init__.py
  16. Android.mk
  17. build-python.sh
  18. create-image-angler.sh
  19. create-image-bullhead.sh
  20. create-image.sh
  21. README.md
  22. run-angler.sh
  23. run-gce.sh
  24. run-unittest.sh
  25. setup-angler.sh
  26. setup-bullhead.sh
  27. setup-gce.sh
  28. setup.py
  29. setup.sh
  30. 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 mainly 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.