commit | fdf2dd809f95cea1285af0ca349eb3068d4a0400 | [log] [tgz] |
---|---|---|
author | Satish Yalla <satishy@google.com> | Fri Jun 28 01:28:22 2024 +0000 |
committer | Satish Yalla <satishy@google.com> | Fri Jun 28 05:01:33 2024 +0000 |
tree | 8c88716d7b91fc55191d445c9907d58a5a00e47a | |
parent | 76ce790b9568f74f2edb6d5539a6b40dcc13cfff [diff] |
Revert "Fix tracking of IP device via their property serial" This reverts commit 2fdace57f77dfc6a4c60c74640b4fec0cc530652. Reason for revert: Droidmonitor created revert due to b/349909926. Will be verifying through ABTD before submission. Change-Id: I6f0c64d0f605bda168e96b87e493fa1126e27c42
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/docs/core/tests/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/docs/core/tests/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.