| commit | d844338a2ca14a0dd74953c2f544326daeb31e5b | [log] [tgz] |
|---|---|---|
| author | Ryan Campbell <ryanjcampbell@google.com> | Tue Apr 04 09:08:22 2017 -0700 |
| committer | Ryan Campbell <ryanjcampbell@google.com> | Tue Apr 04 09:14:30 2017 -0700 |
| tree | 5db5bbbab68e61e1ae899c8501614bfc0b6e57ff | |
| parent | 37585624e857f87f02817191497047335d9e4596 [diff] |
Stabilize the VTS build. Modify the build script to be more stable. Replace unnecessary zip/unzip operations with copy operations. Insert a new phony target to enforce stability (vts -> comp.zip -> vts-framework). Thus, when compatibility zip is deleted, vts-framework target must be remade. Test: rm -rf out/host && make vts -j60, compare to before Bug: 35269811 Change-Id: I926bb47f4b3f2d6fe1fe3e2ab65e053c21570519 Merged-In: I43f5010105cbad7ec770e05e22ab9fb8ca3ff00c
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