Move the netd integration test from vts-kernel to cts-on-gsi.

This test is not appropriate for VTS because it tests the
behaviour of netd, not the behaviour of kernel interfaces.
Thus, when upgrading a device, for example, from 8.1 to 9.0,
the 8.1 test's expectations are incorrect because the correct
behaviour changed when the OS was upgraded.

Bug: 77680167
Test: make -j64 vts vts-tradefed
Merged-In: Ia51874240d0be290bcb43a4f5a8f9cfa9e8d2112
Change-Id: Ia51874240d0be290bcb43a4f5a8f9cfa9e8d2112
(cherry picked from commit 4ff67aa1490090f48301a66911acbab9cb7d4b8f)
2 files changed
tree: 3678a38e1147948ec10aa617e932e35aba360840
  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)