commit | b4272c45d198d10d8a8acaa828a7be7b8ec66f13 | [log] [tgz] |
---|---|---|
author | Sorin Basca <sorinbasca@google.com> | Thu Jan 19 13:32:16 2023 +0000 |
committer | Treehugger Robot <treehugger-gerrit@google.com> | Fri Feb 03 17:13:41 2023 +0000 |
tree | eca985d1dfac4751601628ec4accedede8976ab8 | |
parent | 0924dd23739138f22496202254214114b15c5498 [diff] |
Pin tradefed to Java 11 The master version of tradefed gets used to run tests on all branches. Older branches only have support for OpenJDK 11 and we have to ensure that the framework keeps working even after we target Java 17. Therefore it is needed to pin its binaries to continue targeting Java 11. Bug: 233029164 Test: TH Change-Id: I1f3b9a1f0d807ee0b6c8ba66a1e38d1fe6a45ec4 Merged-In: I1f3b9a1f0d807ee0b6c8ba66a1e38d1fe6a45ec4
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.