commit | 11ba6084cf39495929b6e3acaff385a5c7d4f086 | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Fri Nov 19 14:13:58 2021 -0800 |
committer | Julien Desprez <jdesprez@google.com> | Mon Nov 22 15:58:59 2021 +0000 |
tree | 93e264bcf976db0f6992dc5cca1d89c0b53d6153 | |
parent | ab5c760349aa68805ea5cc6f3975b9c90f09f34d [diff] |
Avoid double teardown Now that avd starts in parent, we don't need this extra logic to clean in case of errors. Test: unit tests Bug: None Change-Id: I539cc57420b7cd6c3b4b1c8d7ad4a1737f7065ac
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.