run hal tests if its test version is x.a and x.b is found where a <= b

Test: make vts -j30 TARGET_PRODUCT=aosp_arm64 &&
vts-tradefed run commandAndExit vts --skip-all-system-status-check
--primary-abi-only --skip-preconditions --module VtsHalPowerV1_0Target -l INFO
Bug: 37903364

Change-Id: I60902f10013ace9bacd4dedb826b0ae4b9cd5ff8
2 files changed
tree: 8cde789045656221f746c6c0771ab197cd266113
  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)