Add vts related artifacts to vts-core package

1. vts-tradefed jars
2. python utils and runner configs (under testcases/vts)
3. kernal tests (under testcases/DATA/nativetest(64))
4. vts target native modules (under testcases/DATA)
5. Update vts-core-tradefed script to support running vts tests

Bug: 149249068
Test: m -j vts-core, check the content of android-vts-core.zip
vts-core-tradefed run singleCommand vts-core -m VtsKernelLtp

Change-Id: Ic0b0191740bc8f707643a9136214857e6f472e09
4 files changed
tree: bfc250e13dbeab8cf39596f392c6340b54659e38
  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)