| commit | e353ee67e1d2ee1e5bb53a0ff8edb39925e26510 | [log] [tgz] |
|---|---|---|
| author | Julien Desprez <jdesprez@google.com> | Mon Jun 03 08:45:02 2019 -0700 |
| committer | Julien Desprez <jdesprez@google.com> | Mon Jun 03 08:45:02 2019 -0700 |
| tree | b864feb308371019811daf24ec2230248113dc20 | |
| parent | ab5a676aaf809b48ded898a23eee3652ee2ae8a0 [diff] |
In VTS layout of testcases/ is different from CTS so address the search When running in the VTS layout, we might not found some of the directory for modules that contains their dependencies. In this case, we do our best effort and use the top level files since lower level files can specify sub-path to be found. Test: unit tests run cts-on-gsi -m CtsBionicTestCases Bug: 130163079 Change-Id: I7b8f2f3e03a0c9852edab5f58ca3a7d76a02fe22 Merged-In: I7b8f2f3e03a0c9852edab5f58ca3a7d76a02fe22
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/