commit | 6362acf6c82ed7282a7427a45867113779f35a94 | [log] [tgz] |
---|---|---|
author | Kevin DuBois <kevindubois@google.com> | Mon Mar 12 16:09:11 2018 -0700 |
committer | Kevin DuBois <kevindubois@google.com> | Thu May 24 14:37:00 2018 +0000 |
tree | 4ab6f31657577c03d4d242665f3433d15eac05f1 | |
parent | 2baa2ae32b850b787875a8ddf2ada27bd95c9441 [diff] |
Have AtraceMetricCollector work with postprocsesing tools. After collecting the trace, allow the metric to use self-contained binaries to process the traces. A fair amount of existing trace tooling is not in Java, and this allows reuse of the tooling without porting. The subprocess results are managed in the same way that the PythonUnitTestRunner works, it will launch the process and then extract metrics and/or result files from the output text according to the defined grammar. Bug: 73541075 Test: 4 new unit tests. Run: tradefed.sh run singleCommand host -n --class com.android.tradefed.device.metric.AtraceCollectorTest Change-Id: I745288edd7e0fc4ca1cd9590ce50a54f107f9933
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/