Avoid using 'su' when running llkd

When VTS is running, `adb root` will be executed prior to run test
cases. So no need to use su to run llkd. Also, in the latest VTS
testing flow, an user build GSI will be used with a debug ramdisk.
In this case, `adb root` works but there is no /system/xbin/su.

Sample error log:
  04-25 14:42:25 E/ProcessHelper: ERROR:root:Failed to start llkd
  04-25 15:58:22.300 ERROR Failed to stop llkd

Bug: 131286127
Test: make vts, run a vts test case to check the above error log no
      longer exist
Change-Id: I4abaf9c83e82529c25a9150ad1dda350025794f0
Merged-In: I4abaf9c83e82529c25a9150ad1dda350025794f0
(cherry picked from commit 9eb19c838bbb9a2206133cd3f1f565858647d82b)
1 file changed
tree: 5241b296e0ce9f58cb6b7137f4164789f4614df9
  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)