package multilib's using different file lab (*64.so) and update
AndroidTest.xml accordingly

the current build rule only packages 32-bit so file

Change-Id: Id1e756d77f09282e69be2d7e86d27fa614b3935f
12 files changed
tree: 51be862c6ac9fe97db456e168e1a0a6ebd0ecc11
  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. .gitignore
  14. __init__.py
  15. Android.mk
  16. build-python.sh
  17. create-image-angler.sh
  18. create-image-bullhead.sh
  19. create-image.sh
  20. README.md
  21. run-angler.sh
  22. run-gce.sh
  23. run-unittest.sh
  24. setup-angler.sh
  25. setup-bullhead.sh
  26. setup-gce.sh
  27. setup.py
  28. setup.sh
  29. 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.