Google Git
Sign in
android / platform / test / vts / 75b5fa9a911c7edccf44f91613c5e426570a0c00
commit75b5fa9a911c7edccf44f91613c5e426570a0c00[log] [tgz]
authorAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Mar 03 07:08:30 2020 +0000
committerDan Shi <dshi@google.com>Wed Apr 08 21:05:01 2020 +0000
tree170addaf3b3904debf5cb71b1495438f814527c3
parent8cea702e335f5afc1053c941231837120e7d2741 [diff]
Fix test suite name to support vts-core suite

The suite name used to be hard-coded. For vts-core suite to run vts
tests, the name needs to be retrieved from TestSuiteInfo.

Bug: 149249068
Test: local run vts-core suite for module VtsKernelLtp
Change-Id: Ic7c7a496d077fd2884f43215d804032381de89ad
Merged-In: Ic7c7a496d077fd2884f43215d804032381de89ad
1 file changed
tree: 170addaf3b3904debf5cb71b1495438f814527c3
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. prebuilts/
  8. proto/
  9. runners/
  10. script/
  11. specification/
  12. testcases/
  13. tools/
  14. utils/
  15. .clang-format
  16. .gitignore
  17. __init__.py
  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)