commit | 99f64e49b68d23df4f50b6dc5f780ba9507f0999 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Sep 22 07:22:23 2024 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Sep 22 07:22:23 2024 +0000 |
tree | fa6d5d369ec6b614aa252e6c95bc756b4648a6fe | |
parent | c3b584a4b49158dceeeb9c710d0883473aba9530 [diff] | |
parent | 11514d1c6aad1dcaad79caa207581e87e2e43aaa [diff] |
Snap for 12386598 from 11514d1c6aad1dcaad79caa207581e87e2e43aaa to busytown-mac-infra-release Change-Id: I9ccd55da08583d0ddc90070af9fa318a6fbb3aab
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.