| commit | ccf42ddeede3c4b5549a3451af9938d470ffb8e9 | [log] [tgz] |
|---|---|---|
| author | Julien Desprez <jdesprez@google.com> | Thu May 14 18:59:28 2020 -0700 |
| committer | Julien Desprez <jdesprez@google.com> | Thu May 14 18:59:28 2020 -0700 |
| tree | 0358fcda8728846a52573278c3fb7c22c3d7db83 | |
| parent | 67342692174b1d8205c2465d80e81deb43163757 [diff] |
Revert the logic for fastbootd in FastbootMonitor Reduce contention on fastbootMonitor, with the change it requires to enumerate all the devices and run a command on each, which is way slower and could cause late updated state, which in turn would release device in bad state or mess up device a bit after being flashed. We will have to re-think how to detect fastbootd continuously. Test: unit tests Bug: 156620327 Bug: 148109220 Change-Id: I68df6c4226ff82c26702fda2655285ce10313594
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.