commit | 7f1ed49c2de4d0e96dbfa36d353f6e658843041b | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Tue Apr 28 10:34:39 2020 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Tue Apr 28 10:35:38 2020 -0700 |
tree | 10d926a09cf761003c0eefc0191b5fd55ff80363 | |
parent | b5e22530c8e3957d79f105a2d0b99f6c23ef05e1 [diff] |
Ensure we don't go into the auto-retry if the runner doesn't support it For subprocess invocation, it's possible that the subprocess runner create attempts, so we don't want the parent to override those. Test: unit tests Bug: 155180527 Change-Id: I933a758118b122a9b63b4c2f0f3f69106b2fd5fc
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.