| commit | c0e985fce2ea91b1e9181d064f1ba4d2ed8f0ff5 | [log] [tgz] |
|---|---|---|
| author | Guang Zhu <guangzhu@google.com> | Fri Aug 16 18:51:21 2019 -0700 |
| committer | Guang Zhu <guangzhu@google.com> | Sun Aug 18 21:00:32 2019 -0700 |
| tree | eeb378001fb6033beb79eb837e8a2733a1102519 | |
| parent | 709631719d6071252cec65600b639b26a18a2d9a [diff] |
use java binary that launched current process for subprocess As a first step of consolidating use of java binary in TF, we are moving away from using the java binary from path; instead we are using the same java binary that launched current process for all subprocess test execution needs. In the future, some of these use cases will be changed to be using java binary based on the API level where subprocess artifacts are obtained (or they'll come pre-packaged with java binaries). Bug: 122862400 Test: existing unit tests Change-Id: I9dc6907cba6af65335ad7e490bb67fbc5b578657
TF is a test harness used to drive Android automated testing. It runs on test hosts and monitors the connected devices, handling test scheduling & execution and device management.
Other test harnesses like Compatibility Test Suite (CTS) and Vendor Test Suite (VTS) use TF as a basis and extend it for their particular needs.
Building TF:
More information at: https://source.android.com/devices/tech/test_infra/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/devices/tech/test_infra/tradefed/architecture
If you are a tests writer you should start looking in the test_framework/ component which contains everything needed to write a tests in Tradefed.