vts: Add util api checkSubstringInCommandOutput which accept specific cmd.

Bug: 140172237
Test: make vts
Test: atest VtsHalWifiHostapdV1_2TargetTest (Test for new
deviceSupportsFeature with specific command)
Test: atest VtsHalWifiSupplicantP2pV1_0TargetTest (Test for old
deviceSupportsFeature with pm command)
Change-Id: Ia657570ccda656270af75760a28ce30e803a04ba
2 files changed
tree: c17b97a4e593b09bac5be578b0536e0b98a16054
  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)