commit | 4efdcf27b34c7f1435fa01eea5604ff9fb7288f6 | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Wed Sep 25 08:48:54 2019 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Wed Sep 25 08:49:55 2019 -0700 |
tree | 5a5f1e7d168ea698e38347267a28f5831dd19f48 | |
parent | c602f01222f1b8d7dfd487455dbd3e20484fadbf [diff] |
Use a more elaborated check for device online in remote Instead of simple key even, use dumpsys which will ensure some level of framework being started. Test: unit tests Bug: 141613258 Change-Id: Ic6ca12c37481f16259df2b1230bfeb6b46fbacd4
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.