commit | 0ebf670dcd46b46ff28fc78f91aeea6777807a75 | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Jun 17 16:44:29 2024 -0700 |
committer | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Tue Jun 18 15:06:20 2024 +0000 |
tree | a74450e11ef1b29259ea0a35925abb5869990799 | |
parent | 870687c80ac079ffc456074b560e06865343faae [diff] |
delete obsolete TODO DeviceSnapshotHandler decides what the snapshot ID is, so we don't need to parse it from the response. Test: n/a Change-Id: I55137b7c67e13ba41d15a87962845e1eba6ec7f4
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.