commit | 8f7f724387d09d7e03a3d40170e874e9bd16bc04 | [log] [tgz] |
---|---|---|
author | Daniel Peykov <peykov@google.com> | Thu Apr 16 16:41:20 2020 -0700 |
committer | Daniel Peykov <peykov@google.com> | Fri Apr 17 13:00:30 2020 -0700 |
tree | ea9912aca5f1a089f3859a7254862003f44a6169 | |
parent | 097ab9cab6fbf010fe72c78d5770f7a13d689436 [diff] |
Allow legacy subprocess reporter to use TF/CTS 9+ methods if possible Also, update comments to reflect that only TF/CTS 8+ is still supported. Bug: 153882415 Test: partial runs of CTS 8, 8.1, 9, and 10 Change-Id: I33cda24b67aaa48fdb88395961793b25e29c3ffc
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.