include arch-specific kernel config fragments

Architecture-specific kernel config options may be specified in
separate files. Include these in the VTS package.

Bug: 62523096
Test: run vts-kernel -m VtsKernelConfig
Change-Id: Ief3be3326a4cfd5659b106026592f9c1f91c6221
Merged-In: Ief3be3326a4cfd5659b106026592f9c1f91c6221
1 file changed
tree: b6741ab80dcccf23f3b6e0a00c8761a55743cd54
  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. web/
  15. .clang-format
  16. .gitignore
  17. __init__.py
  18. Android.bp
  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
  4. VTS Framework Developer Manual