[automerger skipped] Rename vts-core to vts am: 8801fa23b3 -s ours

am skip reason: Change-Id I0e1ef339a21f9fe34cbf0f7a2f3e38fab9250e90 with SHA-1 3298105d19 is in history

Change-Id: I4bf8bfed9e9f831f8b5ef940c6a31126bf02aae4
tree: 1799aa8cb3bd3aa7ab03161d3a524447ec99394c
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. prebuilts/
  8. proto/
  9. runners/
  10. script/
  11. specification/
  12. testcases/
  13. tools/
  14. utils/
  15. .clang-format
  16. .gitignore
  17. __init__.py
  18. OWNERS
  19. PREUPLOAD.cfg
  20. README.md
  21. setup.py
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., record-and-replay and fuzzing) and
  • structural (e.g., gTest and host-driven python) 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.

Table of Contents

  1. VTS User Manual
  2. Where to find VTS test cases
  3. VTS Test Developer Manual (Codelab)