1 # VTS Test Plans 2 3 A VTS test plan consists of a set of VTS tests. Typically the tests within a 4 plan are for the same target component or testing the same or similar aspect 5 (e.g., functionality, performance, robustness, or power). There are three kinds 6 of plans in VTS: 7 8 ## 1. Official Plans 9 10 Official plans contain only verified tests, and are for all Android developers 11 and partners. 12 13 * __vts__: For all default VTS tests. 14 * __vts-hal__: For all default VTS HAL (hardware abstraction layer) module tests. 15 * __vts-kernel__: For all default VTS kernel tests. 16 * __vts-library__: For all default VTS library tests. 17 * __vts-fuzz__: For all default VTS fuzz tests. 18 * __vts-performance__: For all default VTS performance tests. 19 * __vts-hal-hidl__: For all default VTS HIDL (Hardware Interface Definition Language) 20 HAL tests. 21 * __vts-hal-hidl-profiling__: For all default VTS HIDL HAL performance profiling tests. 22 23 ## 2. Serving Plans 24 25 Serving plans contain both verified and experimental tests, and are for Android 26 partners to use as part of their continuous integration infrastructure. The 27 name of a serving plan always starts with 'vts-serving-'. 28 29 ## 3. Other Plans 30 31 The following plans are also available for development purposes. 32 33 * __vts-camera-its__: For camera ITS (Image Test Suite) tests ported to VTS. 34 * __vts-codelab__: For VTS codelab. 35 * __vts-gce__: For VTS tests which can be run on Google Compute Engine (GCE). 36 * __vts-host__: For VTS host-driven tests. 37 * __vts-presubmit__: For VTS pre-submit time tests. 38 * __vts-security__: For VTS security tests. 39 * __vts-system__: For VTS system tests. 40
