| commit | 8240df4d9790ebb1532ab67bfce5544d4373f792 | [log] [tgz] |
|---|---|---|
| author | jdesprez <jdesprez@google.com> | Wed Mar 28 16:57:52 2018 -0700 |
| committer | jdesprez <jdesprez@google.com> | Mon Apr 09 19:22:15 2018 -0700 |
| tree | 5da03951a51c9f5c07d56e52f2611bea7907a930 | |
| parent | ed2e56ee96bc2cc59ec676947ed50d2b8ba010bf [diff] |
Introduce a concept of "fake" devices If a configuration only has one real and one fake device, Tf objects left at the root will not throw an exception, instead they will be associated with the real device. This allows the usage of several <device> tags to download multiple builds, but single device tests can avoid wrapping all their preparers in the <device> tags. Test: unit tests Bug: 74567407 Change-Id: I2cf7bd27e6ee1051ac41abc4d77602fde06208d1
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/