Home
last modified time | relevance | path

Searched refs:VTS (Results 1 – 25 of 35) sorted by relevance

12

/test/vts/harnesses/tradefed/tests/res/testtype/
Dvts_multi_device_test_parser_output.txt1 [VTS-Example] 07-01 08:54:59.495 INFO ==========> SampleLightFuzzTest <==========
2 [VTS-Example] 07-01 08:55:01.215 INFO Exception occurred in command: killall vts_hal_agent > /dev/n…
3 [VTS-Example] 07-01 08:55:01.258 INFO Exception occurred in command: killall vts_hal_driver32 > /de…
4 [VTS-Example] 07-01 08:55:01.296 INFO Exception occurred in command: killall vts_hal_driver64 > /de…
5 [VTS-Example] 07-01 08:55:02.299 INFO sending a command (type SET_HOST_INFO)
6 [VTS-Example] 07-01 08:55:02.312 INFO resp 2 bytes
7 [VTS-Example] 07-01 08:55:02.313 INFO TcpServer Thread-2 started (127.0.0.1:5365)
8 [VTS-Example] 07-01 08:55:02.313 INFO sending a command (type SET_HOST_INFO)
9 [VTS-Example] 07-01 08:55:02.323 INFO resp 2 bytes
10 [VTS-Example] 07-01 08:55:02.324 INFO sending a command (type LIST_HALS)
[all …]
Dvts_multi_device_test_parser_output_timeout.txt1 [VTS-Example] 07-01 08:54:59.495 INFO ==========> SampleLightFuzzTest <==========
2 [VTS-Example] 07-01 08:55:01.215 INFO Exception occurred in command: killall vts_hal_agent > /dev/n…
3 [VTS-Example] 07-01 08:55:01.258 INFO Exception occurred in command: killall vts_hal_driver32 > /de…
4 [VTS-Example] 07-01 08:55:01.296 INFO Exception occurred in command: killall vts_hal_driver64 > /de…
5 [VTS-Example] 07-01 08:55:02.299 INFO sending a command (type SET_HOST_INFO)
6 [VTS-Example] 07-01 08:55:02.312 INFO resp 2 bytes
7 [VTS-Example] 07-01 08:55:02.313 INFO TcpServer Thread-2 started (127.0.0.1:5365)
8 [VTS-Example] 07-01 08:55:02.313 INFO sending a command (type SET_HOST_INFO)
9 [VTS-Example] 07-01 08:55:02.323 INFO resp 2 bytes
10 [VTS-Example] 07-01 08:55:02.324 INFO sending a command (type LIST_HALS)
[all …]
Dvts_multi_device_test_parser_output_error.txt1 07-08 11:56:25 I/VtsMultiDeviceTestResultParser: Standard output: [VTS-Example] 07-08 11:56:25.218 …
2 07-08 11:56:25 I/VtsMultiDeviceTestResultParser: Standard output: [VTS-Example] 07-08 11:56:25.512 …
3 07-08 11:56:25 I/VtsMultiDeviceTestResultParser: Standard output: [VTS-Example] 07-08 11:56:25.515 …
4 07-08 11:56:25 I/VtsMultiDeviceTestResultParser: Standard output: [VTS-Example] 07-08 11:56:25.515 …
7 07-08 11:56:25 I/VtsMultiDeviceTestResultParser: Standard output: [VTS-Example] 07-08 11:56:25.518 …
44 07-08 11:56:27 I/VtsMultiDeviceTest: Standard output is: [VTS-Example] 07-08 11:56:26.877 INFO ====…
45 [VTS-Example] 07-08 11:56:27.147 INFO TcpServer Thread-1 started (127.0.0.1:3617)
46 [VTS-Example] 07-08 11:56:27.149 INFO sending a command (type SET_HOST_INFO)
47 [VTS-Example] 07-08 11:56:27.150 INFO command command_type: SET_HOST_INFO
50 [VTS-Example] 07-08 11:56:27.151 ERROR Failed to setup SampleLightTest.
/test/vts/tools/vts-tradefed/res/config/
Dplans.md1 # VTS Test Plans
3 A VTS test plan consists of a set of VTS tests. Typically the tests within a
6 of plans in VTS:
13 * __vts__: For all default VTS tests.
14 * __vts-firmware__: For all default VTS System Firmware tests.
15 * __vts-fuzz__: For all default VTS fuzz tests.
16 * __vts-hal__: For all default VTS HAL (hardware abstraction layer) module tests.
17 * __vts-hal-profiling__: For all default VTS HAL performance profiling tests.
18 * __vts-hal-replay__: For all default VTS HAL replay tests.
19 * __vts-kernel__: For all default VTS kernel tests.
[all …]
/test/vts/
DREADME.md1 # Android Vendor Test Suite (VTS)
3 VTS consists of a set of testing frameworks and test cases, designed to help
9 VTS has mainly two types of test suites:
14 While the VTS framework and test cases are designed for userdebug or eng build
16 VTS Agent App.
20 1. [VTS User Manual](doc/user_manual.md)
21 2. [Where to find VTS test cases](testcases/README.md)
22 3. [VTS Test Developer
/test/vts/tools/vts-tradefed/res/push_groups/
DREADME.md1 # VTS File Push Groups
3 As part of the test setup procedure, a VTS test can push a set of files to
9 - VtsAgent.push: VTS agent files.
10 - VtsDriverShell.push: VTS shell driver files.
11 - VtsDriverHal.push: VTS HAL driver files.
12 - VtsProfilerHal.push: VTS HAL profiler files.
13 - VtsSpec.push: VTS specification files for all HIDL HALs.
/test/vts/tools/vts-core-tradefed/
DREADME1 VTS Trade Federation
4 VTS Trade Federation, vts-tradefed for short, is the next generation test
5 harness for VTS.
9 It works in a similar manner to the prior VTS harness, but with much
14 - supports sharding a VTS test run across multiple devices in parallel
26 2. Follow the 'Setting up your device' steps documented in the VTS User Manual.
40 downloaded and extracted the VTS zip, the script can be found at
46 'run vts' to run the default VTS plan
63 VTS Tradefed Development
68 The source for the VTS extensions for tradefed can be found at
/test/framework/
DREADME.md1 # Android Vendor Test Suite (VTS) Lab
3 VTS Lab is an open source test serving infrastructure that can be used
4 to streamline VTS and CTS-on-GSI (General System Image) tests.
/test/vts/doc/developer_testing/kernel/
Dltp.md3 0. [VTS Setup](../../setup/index.md)
4 1. [Run all the VTS LTP test case locally](run_all_ltp_testcases.md)
5 2. [Run individual VTS LTP test case locally](run_individual_ltp_testcase.md)
Drun_all_ltp_testcases.md2 ## 1. Compile VTS and LTP source code
8 ## 3. Run kernel LTP test from VTS-TradeFed console
Drun_individual_ltp_testcase.md2 ## 1. Compile VTS and LTP source code
8 ## 3. Run individual LTP test from VTS-TradeFed console
/test/vts/doc/
Duser_manual.md1 # VTS User Manual
3 …ally supported for building and running VTS. Building on Windows is not supported, but it is possi…
16 During VTS test runs, required Python packages are downloaded from the [Python Package Index](https…
56 ### 1.4. Build a VTS package
76 ## 2. Run VTS Tests
78 ### <a name="run_vts" /> 2.1. Run a VTS test plan
140 ### 4.1. Run VTS tests directly for debugging
/test/vts/tools/build/
DAndroid.bp1 // Common build rules for VTS tests
3 // VTS target-side test binaries must use the following for proper packaging:
/test/vts/testcases/
DREADME.md1 In principle, VTS test cases are co-located with their respective projects.
20 VTS codelab, template, tests for legacy components, and tests that are
/test/vts/proto/
DVtsFuzzTaskMessage.proto56 // target product (e.g., VTS)
121 // specification of test suite (e.g., VTS) build target
134 // VTS test module name
/test/vts/doc/testcase_develop_manual/
Drun_vts_directly.md1 # Run a VTS test directly
3 First of all, if you have not done [VTS setup](../setup/index.md), that is required here.
/test/vts/tools/vts-tradefed/etc/
Dvts10-tradefed_win.bat16 :: Can be used from an Android build environment, or a standalone VTS zip
17 :: Caution: Although this script can be used to run VTS on Windows,
49 :: assume in an extracted VTS installation package
/test/vts-testcase/hal/treble/vintf/
DAndroid.bp92 // Should not be used by VTS framework, but could be used for test development.
93 // VTS framework should choose among the other test binaries defined above.
/test/vts/doc/setup/
Dindex.md1 # VTS Setup Manual
/test/vts/prebuilts/libvtswidevine/
DREADME1 The directory includes the prebuilts of libvtswidevine.so used for VTS test
/test/vts-testcase/hal/radio/
DOWNERS1 #Telephony team VTS owners for radio
/test/vts/script/
Dpip_requirements.txt1 # Required packages for VTS Runner
/test/vts/hals/
DREADME.md1 …ct source code instrumentation). Those instrumentations are mostly for the VTS's fuzzing and traci…
/test/vts/utils/python/library/
DREADME.md1 This directory contains ELF parsing utilities for VTS ABI test.
/test/vti/dashboard/src/main/webapp/WEB-INF/jsp/
Dheader.jsp40 <title>VTS Dashboard</title>
45 <a href='#' class='brand-logo center'>VTS Dashboard</a>

12