commit | 48f14b61fde0f40151f501d6c7583aa350054b38 | [log] [tgz] |
---|---|---|
author | Dan Shi <dshi@google.com> | Tue Oct 04 15:28:15 2022 -0700 |
committer | Treehugger Robot <treehugger-gerrit@google.com> | Wed Oct 05 01:50:01 2022 +0000 |
tree | 9465cf5b9a63be98a92ac36dfc7a0d14eba2a9c9 | |
parent | 59b6d50f0c4cd980dabe9cfeb66013029dc8acbf [diff] |
Bug fix in OxygenClient to parse gce-driver-param correctly The start position of `gce-driver-param` options for build info could be at an odd number. We can't assume all params are in pairs. Bug: 250965347 Test: unittest Change-Id: Iedefd16da9c591bc532f80b618696d5d29f0a7f3
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.