commit | 241bfaad81cadcfbc90f016e526ad7b6542f6448 | [log] [tgz] |
---|---|---|
author | Alan Stokes <alanstokes@google.com> | Mon Feb 03 17:39:21 2020 +0000 |
committer | Jim Tang <jimtang@google.com> | Tue Feb 04 15:17:41 2020 +0800 |
tree | 70cdb3c665a66d8583e33e5308c100abe975173e | |
parent | 72af7f9517bde8e17bcd7a11d905164fc28d1dff [diff] |
Minor help text fix. Move the --dry-run option under the section headed "Dry-Run and Caching", because that's where I expect to find it when skimming through. Test: m atest Change-Id: I73877c1b9be5e3d4be484e09736d519e03b06cdf
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.