| commit | 3e498fc93c923ecd93e6c816dbf706015d842039 | [log] [tgz] |
|---|---|---|
| author | Frank Feng <frankfeng@google.com> | Wed Aug 13 17:13:21 2025 -0700 |
| committer | Frank Feng <frankfeng@google.com> | Wed Aug 13 17:13:21 2025 -0700 |
| tree | be12b357c9a5c27cb95e96e9b6c8355a4ba90864 | |
| parent | f79fb56b0b4f913e9a6f1af2783f8d8ddce8ab88 [diff] |
Reformat `DeviceBuildInfo.java` This change is created with "Format Document" of cider-g. This allows use of "Format Document" for future changes without accidentally including white changes. Bug: 417213520 Test: TH Change-Id: Id902618fdcf2ce0187e919346b63181f41a811dd
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.