Include KernelRootDirTest in VTS package

Also copies system/core/rootdir/*.rc files for comparison.

We don't add it into compliance test list because currently Google devices
cannot pass the test (e.g., sailfish), which is tracked on b/64905218.
Will set it as a compliance test after the issue is fixed.

Bug: 64775097
Test: vts-tradefed run commandAndExit vts -m VtsKernelRootDir
Change-Id: I913df1035f4d91daaf3603edab9cfef1409380ce
Merged-In: I913df1035f4d91daaf3603edab9cfef1409380ce
(cherry picked from commit c4beb998fd4c68d064fe0fb2efc9027c40f0b696)
2 files changed
tree: d7368ea324ae9e1174ba1c78929b209ad7cb909b
  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. Android.bp
  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)