commit | c57009decfa788bd495693357ac43c6a73bd801b | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Wed Sep 25 09:00:11 2019 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Wed Sep 25 09:00:11 2019 -0700 |
tree | 9ac9d66f004ab0d4a9f3f84a37492a86d2b872df | |
parent | c602f01222f1b8d7dfd487455dbd3e20484fadbf [diff] |
Don't capture logcat_test if we didn't enter test phase In case of setup error, don't capture a logcat_test as it's confusing. Test: unit tests Bug: 141614546 Change-Id: Ib1966ef1248c70dde41204268abd7e49b26c874a
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.