commit | 67c787fa21b3d94c7b4152c4b64ff3f6243ad3e8 | [log] [tgz] |
---|---|---|
author | Oliver Nguyen <olivernguyen@google.com> | Fri Nov 13 11:49:08 2020 -0800 |
committer | Oliver Nguyen <olivernguyen@google.com> | Thu Dec 03 23:15:24 2020 +0000 |
tree | b061d51d232a88f5a2eee3a38789747975e2bb55 | |
parent | 66ab26c372df267a37bde403af4fcf5a4cf45aa1 [diff] |
No Java coverage measurement no longer fails the test. Since all test types can collect coverage, no Java coverage measurement in the test metrics should no longer fail the test. Test: Unit tests Change-Id: Ie38e5c085254564e18af6e57025be569895f75b6 Merged-In: Ie38e5c085254564e18af6e57025be569895f75b6
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/devices/tech/test_infra/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/devices/tech/test_infra/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.