Remove unneeded pip installs from setup script

Python pip installs occur on the python virtualenv during test
runtime. For users running VTS directly without tradefed,
pypi-packages-local.sh has been added and the manuals have been
updated. Predownloading of pypi packages is handled
in ./download-pypi-packages.sh and ./pip_requirements.txt.

Bug: 36301243
Change-Id: Ide25da97e73006248cd201a8993d75537eccd572
Fixes: 36301243
Test: make vts -j40 && vts-tradefed run commandAndExit vts
4 files changed
tree: 46cfebf393afe709c0b0b4b7aa004d47f63fd147
  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. web/
  15. .clang-format
  16. .gitignore
  17. __init__.py
  18. Android.bp
  19. OWNERS
  20. PREUPLOAD.cfg
  21. README.md
  22. 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)
  4. VTS Framework Developer Manual