commit | f66ae600f93109f4a1a15e4e8207c53f153d6ab1 | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Tue Jun 23 08:24:19 2020 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Tue Jun 23 08:37:16 2020 -0700 |
tree | 100d50cd47d1eec38c93241efd2edfd157a37c41 | |
parent | 69f3855e03ad0f66b625fcc10a46aced9e3e790c [diff] |
Expand identifier to handle Exception -> FailureDescription conversion In some cases, our HarnessException will need to become a FailureDescription, we need the FailureStatus in those cases to carry the type. Test: unit tests Bug: 159457859 Change-Id: I0d175650251275702e1d9cc13d93b6ddcc4ae669
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.
Building TF:
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.