commit | f1e8a981a624711494bdddf34576299d46863ffa | [log] [tgz] |
---|---|---|
author | Hsin-Yi Chen <hsinyichen@google.com> | Tue Jul 02 16:44:36 2024 +0800 |
committer | Hsin-Yi Chen <hsinyichen@google.com> | Thu Jul 11 02:16:02 2024 +0000 |
tree | cf00a46ba9969a8a5bc7242a64adb5f339c23e3c | |
parent | 87988f8d29aa1d2ea6a267cd66706341ee7e6a97 [diff] |
Add build attributes to ClusterBuildInfo Some result reporters implicitly depend on build attributes set by specific tests, build providers, and preparers. To support flexible configurations, Android Test Station lets the users specify the build attributes. TradeFed loads them from TestEnvironment and adds to ClusterBuildInfo. Test: ./run_tradefed_tests.sh Bug: 320862192 Change-Id: Iaea02402d063c6dd6c7fc83e7fe9b3b386824204
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.