Rename VTS to VTS10 am: 0d90e1dfcd am: 728f302ccd am: 384e92d97c am: d826858be7

Bug: 151896491
Test: none

Change-Id: I1d5f43aec02f3232d4233bbcf436121d00ba9643
Merged-In: I9cd76246887622f5a541be38d4b53b8857ee3ade
Merged-In: I1d5f43aec02f3232d4233bbcf436121d00ba9643
(cherry picked from commit e88b1235f7bcc11a70f3462e319edb928666d16d)
31 files changed
tree: 81a389531bba92f47971fb724987b05af3585c64
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. proto/
  8. runners/
  9. script/
  10. specification/
  11. testcases/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitignore
  16. __init__.py
  17. OWNERS
  18. PREUPLOAD.cfg
  19. README.md
  20. 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)