commit | 3b3acc5a485ce7f4cfe487a54b80324d784ea5f9 | [log] [tgz] |
---|---|---|
author | Julien Desprez <jdesprez@google.com> | Thu Jun 18 09:38:00 2020 -0700 |
committer | Julien Desprez <jdesprez@google.com> | Thu Jun 18 09:39:01 2020 -0700 |
tree | 9c640439e3dd8f4a6217f266490eb303b2537035 | |
parent | 5e2848009220d4c82637be252caa6d8ccebc5b4c [diff] |
If we have an instance name always attempt to clean it Even if acloud didn't report it as properly boot, if we figure out an instance name from the logs, attempt to clean them to at least properly set the gce_instance_cleaned flag. Test: unit tests Bug: 159328635 Change-Id: I5cca5f3185180f36230c73add959f1bedf284c3f
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.