commit | 87012c3efec8f5a9c0f0267b803bbd5d9748801c | [log] [tgz] |
---|---|---|
author | James Farrell <jamesfarrell@google.com> | Thu Mar 17 15:51:04 2022 +0000 |
committer | James Farrell <jamesfarrell@google.com> | Thu Mar 17 21:04:36 2022 +0000 |
tree | ccdd8732b65d509a9d6c61a7fc3e26bafeeeb364 | |
parent | d56e3da2b687acec88c5f45476e85cfba37e0dc5 [diff] |
Flip option and getter for exit status workaround. Change-Id: Iace8be3b014de45ea29f67da2b4ed42557a2e6f7 Test: Builds.
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.