| commit | 496ff4f6eba78b1dc5f1e876e10b7da5163c3447 | [log] [tgz] |
|---|---|---|
| author | Remi NGUYEN VAN <reminv@google.com> | Thu Oct 17 16:12:44 2024 +0900 |
| committer | Remi NGUYEN VAN <reminv@google.com> | Sun Oct 20 23:58:03 2024 +0000 |
| tree | 77c880dddb3773b29eab3e78803a17e0eaf98c67 | |
| parent | 6d36b4d86570be0f4494914d2e9eecd843a7df54 [diff] |
Add CONNDIAG log data type and option to use it Add a CONNDIAG log data type for logs output by the ConnectivityDiagnosticsCollector on test failure, and add an option to the FilePullerLogCollector to allow pulling logs with that type (or other types). Test: atest Change-Id: Ib56decb7660e9f93844337fa7a5bf9b00610c1c6
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.