| commit | 3229bf1d8b5c3149a04b3160966d9faa93892d5e | [log] [tgz] |
|---|---|---|
| author | Keun Soo Yim <yim@google.com> | Wed Dec 21 10:32:34 2016 -0800 |
| committer | Keun Soo Yim <yim@google.com> | Wed Dec 21 19:22:07 2016 +0000 |
| tree | 0f7d0e88611d3d573ec85e38f41df68bcdc06f89 | |
| parent | f135da7ff9f877338c4f07143aeae7e5311f44c5 [diff] |
add hal/__init__.py to test/vts so that hardware/interface-side can skip that file. in fact, it'll cause a build error if the same file exists in any other location other than this cetralized place. Test: ENABLE_TREBLE=true make vts BUILD_GOOGLE_VTS=true -j32 && vts-tradefed run commandAndExit vts --skip-all-system-status-check --primary-abi-only --skip-preconditions --module VibratorHidlTest -l INFO Fixes: 33811463 Change-Id: I89072571f60c0037521a0ab7598c8880ebaab187
VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:
VTS has mainly two types of test suites:
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