Read vendor configuration jar into tradefed.

Load the vendor prebuilt config jar and parse the JSON
config it contains.

Test: successfully reads and merges the config.
Change-Id: Id552ebf5c21201a5e378492a3e7828a4d6efd5cf
3 files changed
tree: 1dc6bf72d86cdafa06165620b40be4f11f5b6d91
  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.mk
  18. build-java.sh
  19. build-python.sh
  20. create-image-angler.sh
  21. create-image-angler_treble.sh
  22. create-image-bullhead.sh
  23. create-image.sh
  24. README.md
  25. run-angler.sh
  26. run-gce.sh
  27. run-unittest.sh
  28. setup-angler.sh
  29. setup-angler_treble.sh
  30. setup-bullhead.sh
  31. setup-gce.sh
  32. setup.py
  33. setup.sh
  34. 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.