Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / test / vts / 74e6776f9779f7313dad7f9698e5a1e0121abe85
commit74e6776f9779f7313dad7f9698e5a1e0121abe85[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Fri Jan 13 00:14:21 2017 -0800
committerDan Willemsen <dwillemsen@google.com>Fri Jan 13 00:14:21 2017 -0800
tree2cb0fb52a6cd464cdb0284afa08a00fb23ca2867
parentea6c56a5b9aa50b2bb0110c79e8b549e4ad26891 [diff]
Remove LOCAL_COMPATBILITY_SUITE := vts from lights.vts

It is producing a warning on every build:

  build/core/base_rules.mk:453: warning: overriding commands for target
  `out/host/linux-x86/vts/android-vts/testcases/lights.vts.so'
  build/core/base_rules.mk:453: warning: ignoring old commands for
  target `out/host/linux-x86/vts/android-vts/testcases/lights.vts.so'

And it's already in the test list of native packages to be installed
into android-vts.zip, which puts it into
testcases/DATA/lib[64]/hw/lights.vts.so, which is where all of the push
scripts are already reading this from.

Test: m -j vts, inspect android-vts.zip
Change-Id: Idfa7d4113b4102c0b217026b920f89524b7e3340
1 file changed
tree: 2cb0fb52a6cd464cdb0284afa08a00fb23ca2867
  1. agents/
  2. doc/
  3. drivers/
  4. hals/
  5. harnesses/
  6. proto/
  7. runners/
  8. script/
  9. specification/
  10. sysfuzzer/
  11. testcases/
  12. tools/
  13. utils/
  14. web/
  15. .gitignore
  16. __init__.py
  17. Android.bp
  18. Android.mk
  19. build-java.sh
  20. build-python.sh
  21. create-image-angler.sh
  22. create-image-angler_treble.sh
  23. create-image-bullhead.sh
  24. create-image.sh
  25. README.md
  26. run-angler.sh
  27. run-gce.sh
  28. run-unittest.sh
  29. setup-angler.sh
  30. setup-angler_treble.sh
  31. setup-bullhead.sh
  32. setup-gce.sh
  33. setup.py
  34. setup.sh
  35. vts.mk
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
  4. VTS Framework Developer Manual