commit | c398c17bee54d25adff007ca8539677f7a328079 | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Mon May 15 15:26:30 2023 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Thu May 18 00:05:24 2023 +0000 |
tree | 6dfa6c6d8c257875c1ab09a0b264e1a5368a0a25 | |
parent | a3fa6fc108ccc53a5d7ab45aca62e9a861a1634a [diff] |
Allow optionally to backfill jar with Tradefed ones For test mapping aosp, we might be missing google-tradefed, this logic will allow us to test out the backfill. Test: presubmit Bug: 281690698 Change-Id: Ic7543d66f66ee82e3a17c3224101d22ab0444f4e
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.