Revert "remove legacy mRunName which was replaced with test class name."

This reverts commit 2ebcdfb63542e88e618261d9bb207d48cbcaa61a.

Reason for revert: When the Python runner reports a JSON object with
setUpClass error but no results, the result parser should call
listener.testRunStarted and testRunFailed. It needs mRunName as the
argument.

Test: run vts -m VtsKernelNetBpfTest
Bug: 117129398
Change-Id: I07cc8eaa43eda3d66553268146d21529bac5f6ab
3 files changed
tree: fa80f24c342a1f7d984e501767c1bee01dd86754
  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)