commit | 69437de2eabf82dfc9e99d3d773ad6e2d880e553 | [log] [tgz] |
---|---|---|
author | Frank Feng <frankfeng@google.com> | Mon Jul 26 09:20:47 2021 -0700 |
committer | Frank Feng <frankfeng@google.com> | Mon Jul 26 09:30:16 2021 -0700 |
tree | d7da5e1dd49fe5e309d9765a127997f0cd29d2a0 | |
parent | f6783dcce7c033766d61bda2e8a9bf6dafffe434 [diff] |
Convert to Mockito: ClusterCommandSchedulerTest Test: unit test Bug: 186588563 Change-Id: I9aad8e88d1c3b8c05a0569ca34cf96cf15253693
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.