Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / test / vts / 507bc760721bb1581ef7be6be60abf7a46cc7bb8
commit507bc760721bb1581ef7be6be60abf7a46cc7bb8[log] [tgz]
authorRyan Campbell <ryanjcampbell@google.com>Wed Sep 14 15:30:37 2016 -0700
committerRyan Campbell <ryanjcampbell@google.com>Wed Sep 14 17:57:58 2016 -0700
tree7bd914c83d03ccc9fd846d0cc6a4770fd8753670
parentb8df440391e3aa1df163caebddbc30f5df19e1a1 [diff]
Swap build IDs in table and emails.

Use device build ID as the column header instead of test
build ID. Clean code for clarity.

Change-Id: Ib45f230150932570e58aba045b381c2a4aed1e1b
7 files changed
tree: 7bd914c83d03ccc9fd846d0cc6a4770fd8753670
  1. agents/
  2. doc/
  3. drivers/
  4. hals/
  5. harnesses/
  6. images/
  7. proto/
  8. runners/
  9. script/
  10. specification/
  11. sysfuzzer/
  12. testcases/
  13. tools/
  14. utils/
  15. web/
  16. .gitignore
  17. __init__.py
  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 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.