commit	dd5c7b29103a45940a80f7f00f1fec6c4affce39	[log] [tgz]
author	Hsin-Yi Chen <hsinyichen@google.com>	Mon Apr 10 13:26:52 2017 +0800
committer	Hsin-Yi Chen <hsinyichen@google.com>	Tue Apr 11 14:08:59 2017 +0800
tree	122313e65b1c89623b701ca56d5122121cf47d81
parent	c74a9fb04495d51f297ea5efc9f5873b225aecc6 [diff]

Rename VTS non-compliance test tag The test tag contains '*' which is not allowed for Windows file name. This patch fixes the error creating temp dir on Windows. Test: vts-tradefed_win run commandAndExit vts-codelab Change-Id: I139db21c5630fedf705221a31da958101608ae3e (cherry picked from commit d14455cb38c81e20ee1b66552b34785446b137bc)

tree: 122313e65b1c89623b701ca56d5122121cf47d81

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