build a structure around the VTS compiler

this uses a generator class which can generate some part of
C/C++ header or main body code of HAL and HAL_SUBMODULE for now.
that'll be extended to support HAL_BINDER in the future.
So this architecture generally improves the maintainability.

Change-Id: I4548b5d1abbfac015f36600d8d94c18534da0e3e
(cherry picked from commit b8edda3f3df6daf9b13e600a038fbb3a639dc86e)
11 files changed
tree: f7dc284872f05d421419f28d95348924ff800e6a
  1. sysfuzzer/
  2. testcases/
  3. tools/
  4. Android.mk
  5. README.md
  6. vts.mk
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and testcases, designed to help Android SoC Vendors, Device Manufactures, OEMs, and other partners enhance the robustness, reliability, and compatibility of:

  • the Android system (e.g., HALs and libraries) and
  • low-level system software (e.g., kernel, module, and firmware).

VTS has manily two types of test suites:

  • automated (e.g., fuzzing) and
  • structural (e.g., gTest) testing.

Everyone can download the VTS package from the AOSP website, and run the VTS tests in order to produce a VTS report, which can be submitted to the Android Partner Engineering to obtain a certificate.