commit | 21bb2c7268a1ce97adf9c7a2572955c1f159f203 | [log] [tgz] |
---|---|---|
author | Ziwei Zhang <zhangxh@google.com> | Fri Apr 26 13:04:37 2024 +0800 |
committer | Ziwei Zhang <zhangxh@google.com> | Sun Apr 28 02:57:08 2024 +0000 |
tree | 73f1209a127678da08dfa34159b7af4301509f4d | |
parent | 881e7e168c355a0abc106aa64f44276d83626e6e [diff] |
Keep the directory structure when uploading output files to TFC. Add an option to remove the common pattern in paths. Bug: 332480752 Test: m -j tradefed-all && javatests/run_tradefed_tests.sh --class com.android.tradefed.cluster.ClusterLogSaverTest Change-Id: I82160f089d6244792b46609e4e0a76390ad3a1f2
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.