Add all GSI keys for compliance into VTS package

Bug: 149806657
Test: vts-tradefed run vts -m VtsSecurityAvb
Change-Id: I8289a1ca1e1aa00a15ee8c8985fe7d8926990da3
Merged-In: I8289a1ca1e1aa00a15ee8c8985fe7d8926990da3
(cherry picked from commit 433abbc53b0f45559009028f34ec5485e47372b5)
1 file changed
tree: 80a3030b86b3b5265d67f16086eae23e237a6655
  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)