Fix framework start condition in test.

Without this, VtsKernelLtp waits for ~15 minutes after the end of the
test because the device never reaches bootcomplete, because the
framework is not restarted.

Bug: 134613162
Test: VtsKernelLtp in hwasan build
Change-Id: I09eb1d12db719e0bf2e2e084f7b8e6752c972349
2 files changed
tree: 0c6dc7b2e54601c5d5f3bba83572d02a18089fc1
  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)