| commit | c80dc53609263e084d8957488e2580e77a41b03c | [log] [tgz] |
|---|---|---|
| author | mikehoran <mikehoran@google.com> | Tue Nov 14 14:30:06 2017 -0800 |
| committer | mikehoran <mikehoran@google.com> | Tue Nov 14 17:25:04 2017 -0800 |
| tree | ffb3329562503d1300d749325d4f412b530006a2 | |
| parent | b210bc90c8deaace383026f165b250f7d97bc47b [diff] |
Create tradefed-core target for better atest targets.
This improves build time by about 70% when necessary targets have already
been built. Ensures every target is a no-op and prevents DroidDocs from
building.
Also adds -b and -t params to atest. This was taken from BIT. It allows
a user to specify the phase they want to run: BUILD, INSTALL, or TEST (BIT).
I haven't seperated out the INSTALL phase yet, but this seperates BUILD
and TEST phases. I like this a lot more than --skip-build since it matches
what they are already using and provides more functionality (like
the functionality needed to performance test atest).
Bug: b/69270230
Test: run_atest_unittests.sh
atest -b CtsFileSystemTestCases:AlmostFullTest#testRandomRead
atest -t CtsFileSystemTestCases:AlmostFullTest#testRandomRead
atest CtsFileSystemTestCases:AlmostFullTest#testRandomRead
Change-Id: I336a19b75d16d9839c275829848615e985f14d83
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/