commit | 0c6ff8839b4da2ebb4543ea821e99b1fa0151704 | [log] [tgz] |
---|---|---|
author | Ryan Campbell <ryanjcampbell@google.com> | Thu Mar 30 16:30:22 2017 -0700 |
committer | Ryan Campbell <ryanjcampbell@google.com> | Fri Mar 31 15:05:10 2017 -0700 |
tree | 9826073e1c750b0eac5948d50918217d07f2b3c3 | |
parent | 3cb5442314507c7f2cd900b50799cd8ecdf411d2 [diff] |
Fix coverage processing in VTS runner. Fix a bug caused by using product type from the device instead of the full product name. Fix a bug in the order in which passthrough mode is toggled. Test: run vts -m VtsHalLightV2_0Target (on a coverage-instrumented device) Bug: 36784134 Change-Id: I490500aafab34c0ef4f6fae76c2caa117d6bc6c2
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