commit | 0195990c04588d27f6b21f202a2be68e75731ebd | [log] [tgz] |
---|---|---|
author | Dan Shi <dshi@google.com> | Wed Apr 26 21:55:59 2023 +0000 |
committer | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Thu Apr 27 22:21:54 2023 +0000 |
tree | 67d2a11f3064c90797c9a981e9e9c57acd4f96cb | |
parent | dfb28d5225d4cc8fa361d1908aadb8a93abb3537 [diff] |
Clean up the oxygen version collected from version file Bug: 279611897 Test: none Change-Id: Iae1b77a351fb5863938ef6e84f98e36933ebd704
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.