| commit | 62caacd06e6e7fd275682f11983a66ae4a8804e4 | [log] [tgz] |
|---|---|---|
| author | Xing Dai <xingdai@google.com> | Thu Feb 18 20:37:40 2021 +0000 |
| committer | Xing Dai <xingdai@google.com> | Fri Feb 19 16:07:43 2021 +0000 |
| tree | bc7459b133eb89eaf5d4cac63a179cb7d66dfffd | |
| parent | 1550f03ceddc751e21f010b6bfeb57ea95dd7414 [diff] |
Report device resource to TFC as well. Report extra device info to TFC: 1. TFC will have more information about device. 2. it's easier to add extra infro than add to DeviceDescription. 3. This is also a way to know the host has device monitor enabled or not on TFC side. This is short term solution, long term we need to refactor the gRPC server out of LabResourceMonitor and LabResourceMonitor will only do refresh resource logic. Bug: 178141849 Test: unit test. Change-Id: I2f5280365589839aff4fef22b6e8634d4a89d30f
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.
1. Create your change in Gerrit 2. Add the reviewer named "Tradefed Codereview" (email: tradefed-codereview@tradefederation.google.com.iam.gserviceaccount.com) 3. Review the code review guidance at go/tf-guidelines and go/tradefed-code-reviews 4. GWSQ should add a couple of people from the team to review your code and give feedback.
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.