commit | c4cb3504c0e835b508051f60158cd402fb778184 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Mon Sep 23 23:27:20 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Mon Sep 23 23:27:20 2024 +0000 |
tree | 7570beb12fd16ad203da5abbaca565bb5065eb11 | |
parent | bf11bef6d04f869d3c26b90a7a21e2afb73728f0 [diff] | |
parent | 3cdd21c9c76a1ddb73d8356c79c69e57aa4a1282 [diff] |
Snap for 12404440 from 3cdd21c9c76a1ddb73d8356c79c69e57aa4a1282 to 24Q4-release Change-Id: I51a6b1b553a86319201d3ead29d5bd8bf6fdb20f
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.